Sandra,
I agree with Lanwench, the problem is "procedural" - in a perfect world,
the developer checks out the source, makes his/her changes, unit tests, and
if a large change, sets up or coordinates a system test. Afterwards, it is
passed on to QA aka Quality Assurance, who then does some other minor
testing and promotes to production status, checking in the new source code
and working with the network admins such as yourself to push the updated
program out, whether it be a group of home grown scripts, login scripts, a
PC Tech going to each PC requiring it and installing, or now a days, making
the change to an OU for AD to push out.
Either way, your first stop is to install and force using some type of
Software Version Control, Visual SafeSource is a good start, then remove the
developers access from installing on any "Production
Server/PC/Workstation/Laptop", except maybe their own, unless you have Test
systems for them to use, then remove it from theirs too.
Hence, I'm a developer, and I'm on your side, and yes they'll moan,
gripe and other unmentionable words, but it is the correct and safe way to
go.
--
Star Fleet Admiral Q @ your service!
"Google is your Friend!"
www.google.com
***********************************************