I'm a firm believer in never putting more records in a grid than the user will be able to comprehend. I'm in process of upsizing a VFP system (not my original design) that has the same problem.

My approach is to set up filtering criteria (the WHERE clause) before the data is selected and before the grid is displayed.

Restrict by date range, client name, or something that will immediately bring the dataset down to a manageable size and speed. THEN show the grid.

>Hi,
>I'm still studying and testing in order to transform our application into a client/server one.
>
>Our data centric forms show a pageframe, within the first page there's a grid bounded to the table the user wants to handle.
>I'm in trouble trying to make this grid to work (well) with SPT, since after a lot of reading I've excluded RVs.. or at least I'll try to use them as my last resource.
>
>Actually my grid shows without problem the result of an SPT, but waiting for 10000 records to be fetched is not very fun. :(
>I've also tried to use the "FetchAsNeeded" approach - and it works -, but even if the grid appears immediately, the result is that:
>- you have to wait in order to move to the bottom of the table
>- the vertical bar is not correct.
>
>In a few words I'm in that phase were I'm wondering if I'm tilting at windmills.
>Is my approach practicable or not?
>
>Thank you.