From: liz@paradoxcommunity.com   
      
   Don't forget there can be hard-coded paths - whether for aliases or   
   lookups or RI or some other reason.   
      
   IMO, better to totally isolate them until/unless you're sure there are   
   no issues like those already raised.   
      
   NOTE: IMO, using one workstation for both test/dev and production can be   
   very dangerous - doesn't matter that you have scripts to point your   
   aliases where needed - if you forget you're on production, think you're   
   on test and empty a table, boy are you gonna be mad that you didn't just   
   go with a physically separate box... :-) (experience speaking here).   
      
   Liz   
      
      
   RickM wrote:   
   > Hello all,   
   > Our paradox database has grown well beyond it's initial plan and has become   
   > unruly.  i'm stepping in to try to reign it in.  there has never been a   
   separate   
   > test/dev environment.  i want to set up a separate paradox environment that   
   > will be a copy of the production environment (at least initially) and i don't   
   > want the two systems to ever be aware of eachother or interact.  Can i do   
   > this and still have the two environments on the same LAN?   
   >   
   > They won't interact with each other if they don't access the same data   
   folders   
   > or use the same WORK folder, am i correct?  I realize the BDE's talk to each   
   > other and are aware of each other (how? by broadcast i assume) but i want   
   > to be sure my test environment doesn't interact with the production.  Does   
   > anyone have any tips, pointers, advice?   
   >   
   > Thanks all, have a good day   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)