I have an application that includes (in the application folder) a settings table. One of the fields in this table contains the path to where the VFP data is located (usually on a mapped drive on the network).

Recently I added some functionality to allow users to copy data to their local computer (so that they could work while disconnected from the network). There is a process in which they select the records they want to work with locally and those records are copied to their local VFP data store and deleted from the network location data.

Everything works fine EXCEPT when the user is set up to work with their local data AND the data on the network is also available.

In essence, even though I'm setting up the data paths (using set path, etc), the application appears to get confused on where it should pull data from. For example, on one of the forms no data is displayed while working with local data UNLESS I exit the application, disconnect from the mapped drive that contains the main VFP data store, then restart the app. Once I do that, all of the data populates properly.

This is an old application that has suffered many years of scope creep, etc. As it stands now, I want to find a way to eliminate this issue without having to recode every form in the project, etc (if possible.) There's not alot of money to be made from a complete rewrite and these clients have been very loyal over the years.

Does anyone have any experience with the same scenario? If I need to clarify, please let me know. I had thought about automatically disconnecting from the mapped drive whenever the user chose to use local data, but due to a large number of reasons beyond my control (or choice), that isn't an option.

VFP 9 / WinXP (Development environment and same for end users)

Any suggestions, insight, or information is greatly appreciated.

Thanks,