>Peter,
>this is a limitation of the of the visuall DataEnvironments
>I believe you may have some luck setting it to relative paths using it
>visually.
>What I do is have all my DEs in code and then I just make the DATABASE
>property the database name
>without any path and worry about setting the right path in the main program
>You may be able to achive similar results by hacking the SCXs
>
>Arnon
>
>>
>>Hi,
>>
>>I have what seems like a fairly simple question, but I find it quite
>puzzling. I am going live with my first VFP 5.0 application in a week. I
>want to keep two sets of data. Firstly, the live data which everything is
>set up to now, and secondly a practice database, which contains a copy of
>the complete database for testing purposes. Obviously I want to use the same
>forms and classes in both systems. Back in the Procedural days with Clipper
>this was easy, but it seems even though I have created a practice database
>all the forms are still using the data in the live database. Is there an
>easy way to swap back and forth between Live mode and Practice mode?
>>
>>TIA, Peter Renton

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