Thanks, Jerry, I'll look into this.

We currently implemented quite simple idea, which I invented too: in our System table we added a field, which tells us, if we in production or in Development. We realized, that we can not rely on the server shared name, since it could change.

Of course, it leaves the possibility of copying System table from one server to another (by accident) and therefore overwrite the settings, but hopefully it's a minimal risk :)

Thanks everyone for suggestions.

>>Hi everybody,
>>
>>Here is the our situation:
>>We have Live server, there resides working versions of all our applications+DataBases
>>We have Development server, this has the same structure, as Live, but the current working versions of all applications.
>>
>>Each developer also has its own local system, which replicates the Development server and there are supposed to be the most current versions (versions in work). (I myself found this system to be too complicated, so I usually work directly on Development server, but this is not right).
>>
>>Anyway, my question is: how can we determine, is it Live system or Development system inside the application? The simplest way which I currently implemented would be check to sys(5) (G is our Development drive). Obviously, this is not the right method, since User's could be mapped differently.
>>
>>Do you have ideas?
>>
>>Thanks a lot in advance.
>
>I find it necessary to access the production side on occasions to manipulate data or other things.
>
>I use a method suggested by Whil Hertzen (sp?) in his recent book on VFP development - add a menu to the VFP IDE. Then menu shows the various projects that I work on and offers access to either prod or dev. I merely click the location I want. I can switch projects and sides in the click of an option.
>The various menu options execute macros that set up the prod or dev environment automatically.
>
>BTW - most users I wouldn't trust with access to the VFP IDE on their workstation. Many can barely use Windows Explorer. They run one app or two, and that's it. In one case, however, I setup the VFP IDE on a supervisor's workstation. She has become quite proficient in SQL and uses the IDE to develop queries and reports that are difficult if not impossible to do with FoxFire. The query parser in VFP is limited in some circumstances and access to SQL and the command line is mandatory for her situation. Her exposure to the VFP IDE has encouraged her to go to night school and take computer programming classes. She has the talent and motivation. It wouldn't suprise me if she were to join the ranks of our staff programmers in a couple of years.