Re: RE: Checking Versions out on Terminal Server
Melissa, et al...
Yes, the OWDEVELOPER=TRUE will allow development tool access on a
terminal server, but beware...remember, unless you've set up the terminal
server for development use (doubtful in a production environment),
everyone who modifies, gets, check's out, is changing the same set of
spec files on the terminal server, THE SAME SPEC FILES USED BY ALL OTHER
USERS...and if you've got two or more people trying to modify the same
file at the same time....Well then, why YES, YOU TOO can have the fun of
spec file corruption, and all the wonderful quirky problems, downtime,
unnecessary troubleshooting, package (re)deployments, and the such that
spec file corruption brings to the table.
There are valid reasons that check-outs are not available on a terminal
server by default...in a properly configured system...if a user needs a
different version, he/she can copy one that exists, change PO's and/or
Data Selection, run it, and then request that a version that matches the
new one be created via the normal development cycle if it needs to be
shared by others. This can all be done without turning on the
OWDEVELOPER=TRUE floodgate. That way, production user can create a
version if they need to, and if that version is deemed important enough
to be shared by more than just the creating user, it can be created and
promoted via the proper change management cycle.
Of course, that's just my opinion...I could be wrong...
Dennis Miller...er....Jim
________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit
www.juno.com to sign up today!