>>We seem to have discovered here that VFP5 does not like remote views to VFP5 databases, and I'm wondering if anyone has any ideas what the issues might be here.
>>
>>Our idea was to design our application such that virtually all data is accessed via views. In this way, if we have to do an ODBC link later on to eg a SQL server, all we have to do is redesign the views and not rewrite any -- or much -- code. Seemed like a reasonable idea!
>>
>>In a scenario where our client will be using our program as a "closed" system, however, we want of course to put VFP databases on the server. We have downloaded the latest VFP ODBC driver from Microsoft and seem to be doing everything according to the book, but all of the generated SQL code causes errors of various kinds. However, if I build a remote view to an Access database or a SQL server database, using the respective ODBC drivers, everything works perfectly.
>>
>>Why doesn't VFP want to let us do this with VFP databases?
>>
>>Thanks.
>
>I think you want to use 'local' views for this purpose. Or if need be, you can combine local and remote data in a local view. This way you can either use the Upsizing Wizard to move to SQL Server or as you said, change the ODBC link.
>
>HTH,
>George

Use SQL6.5 Driver.