Thanks for your response Bill. These responses lead me to other questions.

If you fill a grid control with 200 initial records, just to give the user something to look at, how do you then refill it if the user pages down past the first 200 records? Do you just requery, but select another 200 records further down the table?
Cecil

>>What is the best way to handle SQL Server data on a form, with a Remote View, or SQL Passthrough?
>>
>This really depends on your circumstances. If you are upsizing an existing VFP app with a VFP database, remote views may be the fastest route to functionality.

>Otherwise, I would use SQL Passthrough. Personally, I have ALWAYS used SQL Passthrough. It removes another layer of corruptable DBC/DBF data from the mix and lets you use SQL the way it was meant to be used.

>>Also, when you use SQL Server in a Form's Grid control, how much of the data actually comes across the network to the workstation where the user is utilizing a VFP form? Does the data end up in the temp files, until saved and then altered on the SQL tables immediately or later, upon saving?

>This really depends on what you request from SQL. If your grid's datasource is something like Select * from MyHugeTable, you are going to pull all records from the table across the wire.

>If you set reasonable limits on the records you pull, then your network bandwidth usage is minimized. Personally I always limit initial grid displays to something that I assume the user would care to look through (looking at ALL the records in the grid) at a sitting. Bringing 20000 records to a grid is useless since nobody is going to read them no matter what.

>The data pulled via SQL Passthrough winds up in a cursor normally, and those are temp files under the hood. Those files disappear when you close the cursor so housekeeping is not necessary normally.

>>
>>Cecil