There is probably no way around this. As far as the overhead goes, it probably is minimal. Typically, in C/S apps, the concept of next/previous does not exist since the amount of data is considerably more than that in a VFP-data system.

Instead of soley navigating. why not construct a stored procedure that would return key data of the records that match the criteria. Then, when the user selects the desired record, another stored proc will return the entire record to the client. When the user wants to update, another stored proc can take care of that task.



>When I'm using ADO I noticed in the SQL Profiler stuff like:
>
>SET FMTONLY ON
>SELECT MAINKEY FROM STYLES
>
>Fair enough it sends the metadata. But it does this every time
>I move next,prevous (on a Server side cursor).
>
>As far as I recall there is no way to disable the sending of
>metadata each time. Or is there?
>
>Anyone know if this is planned or if you can add a request for future
>ADO versions to do this?
>
>As far as I'm concerned this only needs to happen once when you open the
>cursor. Ok maybe a column type changes but we shouldn't do this while the app is runnnig any ways.
>
>I suppose the overhead is minimal or is it?