I just don't get it??

From what I see there is no simple way to switch all of your local views to remote views without creating another set of views. There is not some simple 3 line property change like what I can do to switch connection strings to do this - your stuck creating another set of views...thus doubling the workload anytime you make structure changes.

>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.

What do you mean by "one location" ??
And yes I realize that using the remote views limits me to VFP6 features - but that's not been a problem for me and by doing so I've made switching backends seamless. The slower data access is so miniscule (if there actually is any) that's it not even noticeable to the user. As for the memory - well if the views are designed properly it's not that much memory and PC's these days come with more than enough memory to handle these things without having to worry about it. And how does a remote view use more memory than a local view anyway?
Sorry to keep pestering you but I really want to understand all this :)


>>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.