Sorry for not answering your question, but… who needs VSS?
This system is not quite reliable, overly intrusive and contains number of critical misconceptions; and one of the most dangerous misconceptions is this: checking in of the changes to a code base is not transactional. It means that if something bad happens to one of the computers or connection, only part of the changes can be committed, which can end up in half-committed and hence inconsistent change.
Another frustrating misconception (related to the one explained above) is that the changes, changes history and related information is considered on per-file basis.
All these and other problems make VSS only seemingly usable, and people who think it's fine are almost those not familiar with real Revision Control Systems, which can be really robust and light weight at the same time, also non-intrusive, so they don't modify the nature of programming activity.
Also, I think it's too risky to trust your valuable programming asserts to a proprietary solution. The Revision Control System should be Open Source (and most of them are these days).
Please see this discussion and references on this page:
Revision control systems, which to choose from?[
^].
—SA
Submit an article or tip