>The REMOTE clause requires a CONNECTION clause according to the developer's handbook. If I remember correctly, the benefit of a remote view is that the remote DBMS does the SELECT and sends back just a subset of the data - thereby reducing network traffic and speed of operation. Hence, I think you have to have some process running on the remote machine to accept ans process the SELECT and other commands. Therein lies ODBC (or SQL Server).
>
>What horror stories have you heard re ODBC? I saw the ODBC driver for VFP at Microsoft. Is this for VFP as a back end or as a front end only?

John

The horror stories were mainly with 'other' vendors ODBC driver revisions. Do a Search here and you should find a few people desperately seeking help.

You got me curious so I looked into what your doing (or think your doing). Even though the words are 'local view' it really refers more to a local 'type' of data. A local view should work for you. Still only the View matches should be downloaded to the local PC so (hopefully) taffic should not be a big concern.

The FoxPro ODBC that ships with VFP is for Fox 2.x table types. If you do try another option you may be better off to look at SQL Server.

But I still think a local view will do what you need & do it reasonably well. Matter of fact if what your doing just a one way operation (no update to the original table) then a plain old SQL to a cursor may be good enough. Just SQL to a cursor the records that are not there using an outer join & then appending the recs to the table you need to update.

Hope I did better... (s)

Tom