Hi Bob,

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.

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 ;-)



>>Remote Views are going to be awkward to work with in a physical n-tier design as they cannot be used by anything but VFP components. I think I would recommend becoming familiar with ADO in that case. Remote views work best in 2-tier situations.
>
>
>John,
>
>I beg to differ. Remote views can be used in a middle tier the same way they can be used in the front end. I personally thing doing this...
>
>vp_CustID = 123
>use v_Customer
>
>replace Blah with Blah, ;
> Blah with Blah, ;
> Balh with Blah, etc
>
>lSuccess = tableupdate()
>
>Is easier than using SPT and building the Update query string. Granted, you won't have access to the remote view in the UI, but that is a different issue.
>
>BOb