>>Hi,
>
>>I have a Novell Network and have the same problem. I've solved this by simply mapping a drive letter to my test enviroment and another to my live directory.
>
>>I made two map files (.bat files) as follows:
>
>>testData.bat
>>map root q:= f:\develop\testdata
>
>>liveData.bat
>>map root q:= f:\apps\vpmason
>
>>NOTE:
>>You have to make sure all references to the dataenvironment is to q:\ and not to the mapped 'REAL' directory. In other words, if the .dbc is called myDBC the dataenvironment and all tables must reference q:\myDBC and NOT f:\develop\testData. If you do this - have fun...
>
>>Thats it! Before entering the environment for development I simply choose if I want test or live data.
>
>>In my network login script q: is always mapped to f:\apps\vpMason. That way all the users on the network are using the proper data.
>
>>Robert
>
>Robert,
>
>Thank you very much for your reply. I have had four replies, all of which are workable solutions, but I think yours is the simplest and most elegant.
>
>I have one question, though. Do you always recompile everything before testing and then run the program through the .bat file. So, you never try and run anything from within VFP?
>
>Thanks again,
>
>Peter

Peter,

One other thing, do not run the .bat file from within vfp. Run it before entering the development or the live. If you have it as the default in your network login, you don't have to do anything for live or developing. If you are working on something new, and want to test it and are in the LIVE data, exit vfp, run the .bat file and reenter. Very simple.

Robert