Oh my, no. Tables/database, etc should be opened in one location. Again, your way will have slower data access and limits you to VFP 6 and earlier features. It also takes more memory.
>I still don't understand - all that does is indicate if you open local views or remote views? Still sounds to me like you need another database with all new remote views and then one for local views plus code all over the place saying which ones to use. My way its the same set of views no matter what it's connecting to and its a total of 3 lines of code to make the switch...plus everytime there is a structure change I only have to make change in one place - this way you'd have to do it in two places.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer