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.

>It's in the datasession.OpenViews property
>
>>I've rarely had table corruption myself with the exception of one client about 10 years ago- and they had it several times a day, everyday - thus having to kick out 400+ users several times a day to reindex tables (which is why I think they fired the guy and hired me to fix it). The fix was to use remote views. HUGE difference between having the ODBC driver open the table and VFP open the table. I don't know how the internals of VFP work - but I know that this fixed my clients problem.
>>
>>Plus...what is the property change to switch local views to remote views and set the connection strings for them? I don't see an easy way to do that??? Unless I'm missing something here I don't see how this could be as easy as the 3 lines of code needed to switch the connection string like I have below.