https://www.infopathdev.com:443/forums/40.aspxFor browser form specific questionsenCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/100801.aspxMon, 19 Jan 2015 23:46:14 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:100801Patrick Halstead0https://www.infopathdev.com:443/forums/thread/100801.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=40&PostID=100801<p>&nbsp;The key thing is 1) to reduce the amount of data displayed in a dropdown - since each entry eats up a Windows Handle, and 2) to reduce the amount of data getting pulled in using filtering by setting the query fields before calling (in other words, don&#39;t&nbsp;pull everything in by default on&nbsp;load).&nbsp;</p>https://www.infopathdev.com:443/forums/thread/100760.aspxWed, 14 Jan 2015 12:54:47 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:100760BejeweledOne0https://www.infopathdev.com:443/forums/thread/100760.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=40&PostID=100760We have a form that loads extremely slow. Upwards of several minutes to load. We have tracked this back to one of our drop down lists. This is a cascading drop down setup that has 8 fields. The list has 2341 entries in it and it has been indexed. I know that people have forms that deal with extensive amounts of data. How can we accommodate this data and the cascading drop down setup and still have the form load in a reasonable amount of time?