>Dude, use the view! In a view you can tell it the volume of data to return. If you like 20, then so be it. This will work on local as well as remote views.
>
>DBSetProp('SUMVIEW', 'View', 'FetchSize', 20)

Hm, when I tried this, but it didn't affect the speed any. Let me make sure I followed you correctly.

I created a view. Selected all fields. Set my filter. Set the order. Saved the view. USEd it with the NODATA option. Cut-n-pasted the DBSETPROP() line from above. Then did REQUERY().

That's okay though. I know how to optimize native Fox. I was just hoping I could find a standard method to use for both. The client wants the initial product to use native Fox immediately followed with the next version that will be C/S.

Thanks for the help.