>>>Because your view would actually be an ADO recorset and you could pass it to front/end clients or middle tier components that want records set data.
>>>
>>
>>But you can just use a regular ADO recordset to do that. The only advantage I can see to something like this is if it would allow us to bind VFP controls. Otherwise, what's the difference?
>
>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.


That's exactly what I was trying to say....
Thanks BOb

>BOb