InfoPath Dev

I am creating a non-browser based InfoPath form (InfoPath 2007 SP2) and so far I have about 500+ fields, most of which will have formulas with filters in them.  I'm testing it out with Preview after I have entered in but just a few of the formulas into the fields - this is where I am noticing that when trying to input data into the form, it's REALLY sluggish - moving from one field to the next is slow and takes 2 or 3 seconds before the cursor shows up so I can enter data.  It wasn't doing this sort of thing until after I added roughly 400 additional fields.  These fields are all in their own view

I have 3 views: The input view only has 27 fields in it within 11 different repeating tables - that's the view that is SLOW when entering the data.  The other 2 views are all read-only fields, but something very odd - when I uncheck the read-only property and test the input in the fields on these other two views, there is NO PROBLEM with the slowness I am experiencing with the input view.  Does the slowness have something to do with the fact that the input view fields are within repeating tables?

I also have all of fields categorized into folder groups.  The 400 fields are all in one group folder, each of the 11 repeating tables along with their fields are in their own 11 folder groups. 

I'm not pulling data from anywhere or anything like that.

 Hi,

 I completely understand performance problems you are facing with InfoPath when large forms are in play. I have developed some forms for my company which contain about 3500 fields each! In fact, about 1500 are actually being used for entering data, and others are read only. InfoPath has some serious problems when such scenarios are in play.

Not to go into details further, here are some of my experiences:

-  Field (attributes) are performance killers! - Make sure you are not using a lot of attributes in your data structure to/from which you read/write! For some reason, any operation on the form takes a lot longer, if your data structure contains large number of attributes.

- Conditional formatting can slow down your form! If you use a lot of conditional formatting it may create performance issues. For example, if ou have 10 checkboxes and want to disable some of them when one is clicked it will, from my experience approx. double the time from clicking to the point when formatting is completely applied. I guess this could be the case for you, since you are using multiple repeating tables in one view which is also in a way formatting. Maybe the solution would be to split them in multiple views and test your performance.

- Multiple rules can also create performance issues. Especially if they trigger other rules and conditional formatting on other fields and controls.

- Machine. I noticed that performance is highly dependant on the machine. I develop on 2,2 dual core processor and 2Gb RAM. Comparing with Intel Atom 1,6, 1GB (netbook), it takes 2 seconds more for certain actions to perform on the second machine.

Of course, the worse thing is when you have mix up of all of these, as it was in my case. I suggest you do some profiling on your view, by removing certain functionalities, and measuring performance. That way you will be able to determine what exactly slows it down.

 Good luck!

I had this happen on a form that had a drop down list control that was set to display unique entries only. The data source for the drop down had a lot of rows, and displaying unique just KILLED my form performance. See my blog post here for more. Don't know if this particular scenario applies to you, but thought it worth mentioning.