Local views are used when you're working with native FoxPro data. Remote views are used when you need to access data in another database (SQL Server, Oracle, Access, etc.) using ODBC. You can also use remote views to access native FoxPro data through ODBC, but this is not the most efficient way to access VFP data from VFP.

You didn't really give enough information to determine whether this app is a good candidate for client/server. The tables certainly aren't that large but there are other considerations for client/server such as security, reliability, performance over a WAN, etc. If you want to use this application as a way to learn client/server it might not be a bad idea. Keep in mind that for a system to be client/server it must have a server database like SQL Server or Oracle. Just because the application runs on a client and the data is on a server doesn't make the application client/server.

>When do you use remote views instead of local views? What is a local vs a remote server? I'm developong and app to run on 4 computers networked with and running Win95. The orders table will have 40k records and will add 20k per year and the orderitems will have 600k or so and add 345k records per year. Should I set up parametized remote views instead of parametized local views? I want to learn Client/Server is this app a good candidate or no? Thank you very much.
>
>Note: I kept seeing the word 'large' describing SQLServers, remote parametized views, client/server, etc and finally on page 512 of MS VFP Developer's Guide they give an example of 'large' as a 10M record Customer table and a 100M record Orders table. Am I looking to fry too little of fish in a large pan? Even if so I want to learn.