We have a data access object that forms a layer between the interface and the data whether it be file share or SQL Server data. Native intelligence in the object properly handles the request. With the reset of a single parameter in the application object, the app switches from file share to SQL Server. That said.

If your data is always represented by views, remote or local. You access the view like you would any local table. When your user appends a record, changes a record, or deletes a record, the change buffer is set to "dirty". A tableupdate on the view is propagated back to the data source, and the specifics are handled by the Visual FoxPro data engine. Hence, if you always represent your data by views, whether they are local or remote is largely irrelevant.

Regards,

Jason