You may trick it by setting a local view on a rempte view.
as long as the local view is bound to your controlsources you me re use and redefine your remote view as long as you like.
IOW Define a local view that gets the data from the remote one. (In the moment of definition all what you nned is a cursor that looks like the remote view)
Later at using this, define the remote view at your needs for the moment. Get the data from the remote source. Use / requery your local view. If you need tho get another piece of remote data, close the remote view, redefine to your needs and get the data. Recquery the local view.

To write data ,you need to write from the local view into the remote view and from the remote one to the remote data.

This all sounds possible but I would avoid it.

If I was you, I would start a new thread asking how to handle remote data with the needs you have. (You will have better words) This will attract the right people.


Agnes

>Agnes, thanks for the reply.
>
>>>But this for native views.
>
>For your problem it seems that the &lcWhere is send to the remote source without expansion, what will cause the error. IOW I read the error message like: VFP will not expand the macro for remote views.>>
>
>That is my experience so far. Can anyone else confirm that macro parameter expansion is not possible for remote views, or is there a way around this problem?
>
>>>The only thing I have heard of are store procedures on the remote side. But I have never done things like this.>>
>Me neither, and I don't want to get into these things at this stage. I would rather concentrate on front-end development and leave the SQL stuff to the DBA staff.
>
>Regards,
>Alan