>ADO can handle this for you. Look at the help files.
You have to go to MSDN and see ADODC to learn about 'RecordSet.Refresh;. Is the object we're all talking about the:MSAdodcLib.Adodc.6?
So Graig,
A developer could conceivably develop one interface, with ADO COM, to service data requests (via store procedures and a VFP 'thick client'), that could (both) work inside a firewall AND accross an ISP, right? The same 'program' would work regardless of its proximity to the 'backend' odbc. It almost seems that c/s applications should more or less rely on ADO for almost all the data stuff in order to be 'boltable' to a variety of architectures.

Do you see much difference between the way a pass-thru cursor behaves, and the way an ADO RecordSet behaves. Is performance noticably degraded when stored procedure calls are required to pass through an ADO COM layer?

Word!