>1) I understand with C/S you want to pre-qualify your data to keep the result set as small as possible. What do you do for controls like listboxes where you can't can pre-qualify and you can't limit your record set? For example, I have a LoadStatus listbox which is currently using rowstat.dbf as the rowsource. If rowstat.dbf has 100 records and VFP is set to fetch 100 records at a time...?

You can limit the amount of data that is used to populate the listbox. If you populate the listbox with a remote view, parameterize the view to filter you data.

>2) What should you do, in general, for cases where you absolutely can not pre-qualify your data? For example, in our current system, we have a Load Tracking form which tracks different shipments. This form is using a grid to show load information. Is this OK since VFP is set to only fetch 100 records at a time?

When you say "VFP is set to only fetch 100 records at a time" are you refering to the FetchSize property of the cursor. The FetchSize property drives the progressive fetch feature of VFP's database engine. VFP will bring down the first 100 rows (determined by the FetchSize property) and then release the program to continue. VFP will continue to download the rest of the result set in the background.

Are you sure that you cannot limit the data that is downloaded from the server for this operation? Can you only show one load at a time?

>3) What do you do for search lists? For example, say you have a Client form which allows you to add/delete/modify company clients. If the user knows the name of the client he wants to modify, you can pre-fetch that way. But, what if the user wants to browse through a user search list and select one? Once again, will VFP take care of this since it is only fetching 100 records at a time?

I like to present the user with a search form and let them specify some criteria to limit the information being downloaded. Again you can use a parameterized view or construct a pass-through query. Something like a QBE form

-Mike