>If you read through the thread, it appears that Jane is going to be working in a component architecture environment. The point I was trying to make is that, in that environment, you may have to pass blocks of data around between components. That is not possible, as you pointed out, with remote views. The only common ground of the three types of remote data access for this type of application architecture is ADO.
>

Somewhat Agree!

While EXTERNALLY you may be passing ADO, that doesn't mean you can't use views and native data access etc. Espessially if you are using VFP native data. Since using ADO to retrieve an manipulate that data gives you two performace hits... 1) You are using the VFP ODBC driver and 2) ADO uses COM and there is an overhead to using it.

>OTOH, you can play mix-and-match. If you have, for example, a middle-tier component that goes out and summarizes server data and returns a single value or a preformatted list of values then, heck, make it a VFP component and remote view or SPT the hell outta it ;-)
>

YES! This is the way, internally use all that VFP gives you... if you HAVE to return a recordset create it from your final 'crunched' cursor. I guess that is what I was trying to say.

Also, there are methods to pass data without using ADO... er, XML comes to mind.

BOb