InfoPath Dev

We modified the massive core.js file to not instanciate the HTML editor until you click into the field.  This greatly reduced the leak when opening the form and viewing the information.  And when the form is closed, as long as the user didn't click into a field, the memory that was used is garbage collected and can be used ...

I've already done a diff on the .js files in SP1 beta and it doesn't have anything that looks like it will improve performance from the hotfixes we already applied.  Predicting when it will be released is futile. Now if MS could fix the memory leak with rich text boxes... John

That patch you found is very important.  That has a change that increases performance by 2 to 3 times.  The SharePoint SP1 Beta has another change that improves memory leaks if I remember correctly.  It doesn't eliminate them but greatly improves them.  We had to manually change these files to fix which was very ...

Try this... http://www.infopathdev.com/forums/t/6588.aspx

SharePoint email configuration doesn't provide a place to specify a username and password which is required for Exchange to send out email to external mail servers.  This had to be locked down to help prevent spam so there is no way around this.  Mail servers will not send out external email unless you log into them with a ...

Use both IE Spell and http://www.ie7pro.com/.  IE Spell has an issue where it clears out the entire text box when it corrects more than one word.  ie7pro doesn't spell check rich text boxes.  That is why you need two of them. If someone has a better solution let me know. John

Have you found an answer to this yet?  From my research there are no work arounds for browser based InfoPath forms.  See my post on the memory leak with the rich text editor. John

You need to have the latest patches and I'd recommend using the beta SP1.  The beta SP1 has a few changes to the core.js file that are extremely important and for us made the forms run 2-3 times faster.  Also KB933566 is very important. C# code runs quickly but rules and validation can impact form performance significantly.  ...

We are having a significant memory leak on browser based forms that use the Rich Text boxes with IE7.  When we switch views it adds 35K of memory to the iexplorer.exe process and this memory is still pinned even after closing the form popup window.  As the users use our system and run close to the memory limits the window/Form Services ...