Listen to a good friendly advice:
never ever use Microsoft VSS. Not only it is obsolete, it used some bad misconceptions in first place. One important fallacy is: it is not transactional. Also, it is bloated and proprietary. Moreover, I know some people who really badly suffered from VSS malfunction.
Please see this discussion:
Revision control systems, which to choose from?[
^].
See also my past answers:
Needs some words of wisedom to set up and/or use a server[
^],
Make an unclickable form[
^],
How can i structured to arrange sources code when i create a new solution[
^],
Reviews at Apache Subversion[
^].
I don't say that I specifically advertize Subversion or something in particular. But pay attention for my motivation of requirements for a Revision Control system and the value of open-source solution in this particular field.
I would also add: if you are not using some Revision Control System, you are not really doing programming. Your valuable code asserts not belong not to you, but to every software or hardware failure and every your mess-up. You need to stop doing what you are doing and start working with some good Revision Control System as soon as possible.
—SA