Re: Visual SourceSafe for Documentation Source Control

["Gene Kim-Eng" <techwr -at- genek -dot- com>]

Our company had numerous instances of accidental deletions and 
overwrites of source files until we began moving the final versions of 
projects out of VSS and into a fully secure document control system.
It may not be obvious to the day-to-day user, but VSS does not have
controls to ensure that deleted files are not purged from its database so
that they can always be undeleted, or to ensure that renamed files will
always be linked to their previous named versions to preserve their
histories.  

Gene Kim-Eng


----- Original Message ----- 
From: "Zbyszek Cybulski" <z -dot- cybulski -at- gmail -dot- com>


I don't agree with your opinion. A VSS database administrator can
grant users the access to projects/files in the database. This is how
it works in my team. There are users who can get the source files but
cannot modify or delete them. The others can modify but cannot delete
files or modify projects. And, of course, there are the projects
owners who have the full privileges.


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Try WebWorks ePublisher Pro for Word today! Smooth migration of legacy
RoboHelp content into your new Help systems. EContent Magazine Decision-
maker review (October 2005) is here: http://www.webworks.com/techwr-l

Doc-To-Help 2005 converts RoboHelp files with one click. Author with Word or any HTML editor. Visit our site to see a conversion demo movie and learn more. http://www.componentone.com/TECHWRL/DocToHelp2005

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.