>>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 your routines and to other processes as an object.
>>
>
>Yes and no. IMHO the main reason to use ADO is because it is portable (in the recorset form) from one environment to another. Actually ADO doesn't 'objectify' the data, but gives you an Object Model to access the data.
>

Read my post again. This is almost exactly what I said.


>>If you want to manipulate data using VFP DML, why not create a remote view?
>
>If I want to create a common component that perhaps a VB and Java and and ASP front end are going to access, I need to pass the data in a form all front ends understand. Basically you could pass all the data as a string. But, if you pass an ADO recordset, the front end does what it needs, and passes it back.

Right. If you want to pass your data as an object or use it in different processes, use an ADO recordset. OTOH, if you want to manipulate it in VFP with the VFP DML, use 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.
>
>As it stands, to do the above you have to convert the data you collected in your view into an ADO recordset to pass. Wouldn't it be simpler, if (which it is pretty close already) you could somehow instruct the view to USE an ADO recordset instead of a VFP cursor?

ADO is not just a way to compose data, it is also a way to access it. You don't have to first define a remote view, query it, and convert the results into a recordset; you can just define your ADO recordset with the same query parameters as you would put in your remote view. IOW, to use ADO, you don't have to use remote views, and vice-versa. They are two different roads to the data, and I still don't understand why they need to be combined.

I apologize if I am misunderstanding your point.