I have read the fine book "Client-Server Applications with Visual FoxPro and SQL Server 7.0" and thought that a remote view of the SQL database would be perfect - I would just make a view of the entire remote table and the code wouldn't even know or care whether it was working with a remote of local copy of the data. Of course I'm doing all this on a single development machine and everything looks great now...

However, I have this bad feeling that when a real user is connected to a really remote database that awful things will happen - like a tremendous delay to download the whole database when the view is opened or when a record is saved???

Is all this accurate? Should I start reading about ADO? Is there a good way to make the code semi-transparent as to whether it is working on a local database or a remote connection?

Thanks (I'll keep reading)
Pat