>What is the compromise? The overhead of maintaining all those view? Your suggestion is what I had originally planned on doing -- until the advice that I received. This system I am building will have more than 50 tables & views by the time it is finished - and that will be a lot of views to maintain. I can deal with that -- but if performance suffers, I'll may be stuck maintaining 2 different versions of the application -- one for VFP and the other for Client/Server.

As you have been advised... program your systems using local views.. however, design it and the interface like you were only accessing remote data. What I mean by this is that NO view or query should bring back an entier table, unless you know it will be under a few hundred records.

This also mean paramaterize your picklists if the picklist is going to be against a table of 20,000 records, you don't want to bring all the records accross.

Also, make sure you only include the fields in your query that you need. For example, have one view for your picklis that only has ID, LastName, FirstName.. then, for your data entry for you pull all the fields, but you are only pulling info for one person.

HTH,
BOb