>The difference is, you have to code ADO recordsets seperatly from normal views and tables. The power of VFP is that remote data can be manipulated with NATIVE foxpro commands. So, why can't using an ADO recordset be as simple as using a View or a Table? Now, you have to do all these conversions, or you have to write ADO code. Or, you have to write your own wrapper class so that ADO works with the commands you are familiar with.

The only work I have done with ADO is personal experiments for learning purposes, so humor me here...

Isn't the purpose of ADO to be able to deal with remote data in an object fashion? I mean you can define the recordset, create it, and iterate through it with FOR EACH, set it's properties, and pass it around you routines and to other processes as an object.

If you want to manipulate data using VFP DML, why not create a remote view?

I mean, I think we already have the power to do things either way. Why would you need to manipulate a recordset using the VFP DML? I still don't understand the need to meld the two data access methods into one hybrid.