>I have a few questions regarding Microsoft's VisualSourceSafe....
>1) Rather than having 8 developers setup working folders locally, does it make sense for all developers to have the same working folder which would be a DEVELOPMENT db on our local network? Then we will also have a CURRENT db (which contains all the live projects) on the network as well. We would never change anything in CURRENT, we will only make changes in DEVELOPMENT. Once changes are completed in the DEVELOPMENT directory and tested, they can be moved to the CURRENT folder. That way we don't have copies sitting in 10 different places.
>2) How do we effectively use VSS to get all programming changes live? What is the best way for us to be setup to do so?
>3) I know we can set labels & versions to all our changes, but is there anything built in for complete documentation purposes? Currently, our version control has a documentation field. If a change requires new documentation, we check a checkbox to alert our documentation staff that a documentation change needs made before a program can go live. How will our documentation staff know that a change needs made to online help or to our printed help manuals?
>
>Thanks.

Try a quick look at the vault on http://www.sourcegear.com/vault/

Free for 1 user. Uses SQL Server for it's data. This way you can query against it for your help desk.