I would strongly discourage from using Microsoft Source Safe. If you can, do yourself a big favor: save your development from big troubles.
Among other problems and misconception of this proprietary software, at least one is really critical: lack of transactional approach. Some of my colleagues reported serious loss or mess-up of their data.
I also personally think that code asserts are too valuable to trust any proprietary solution; the revision control should be Open-Source. These days, there is a good choice of powerful, light-weight, non-intrusive, portable, extremely reliable Open-Source tools. Please see this discussion:
Revision control systems, which to choose from?[
^].
Here I answer related questions on particular tools in more detail:
Needs some words of wisedom to set up and/or use a server[
^],
Make an unclickable form[
^].
And here I explain why not VSS:
How can i structured to arrange source code when i create a new solution[
^].
—SA
Submit an article or tip