InfoPath Dev

 Hello everyone,  I was curious to know if anyone could share any best practices with regards to handling databases with large volumes of data. 

I"m working on a form that will connect to a prospect database which contains well over 20 attributes per prospect, and has approx. 14K rows ..  

Obviously, in its current state, just hitting the query button will take a long time. I'll plan on breaking it up into smaller tables with various attribute groups and hope that will help..  but in terms of filtering the data, . is there a good way to only bring back a set amount of data at a time rather then the whole shebang? Like just show the first 100 rows and perhaps previous and next buttons. My primary key is an autonumber

 Thanks!!

**Update**

I think I"ve managed some success by creating buttons that will query based on the prospect name..  i.e. Show only "A-D"  "E-K",  "L-R" "S-Z",, but I'd still be interested hear of alternative solutions other users may be implementing.

Hi Desmo,

Here are three best practices:

• Use a Web Service to enable a) parameterized filtering, b) browser support, and c) data-level abstraction (Qdabra's DBXL is a good example and handles large datasets for many companies today)
• Save XML data to database for 100% fidelity on subsequent opens (data types roundtrip without any issues)
• the XML data is mapped to SQL by Web Service
• loose coupling enables data schema changes later without form migration or interruption of your business process
• Prevent locking issues by restricting access to InfoPath client (or Web Service that locks data for InfoPath

Best of luck!

 Very helpful thank you