Come on now, I didn't call you an idiot.
No, *I* called me an idiot and put the words in your mouth. :-)
What I may have failed to mention (or did, way back in the mists of time -- I forget) is that I used to use VSS. Actually, our whole team did. For three years I lived and died alongside VSS in a six-member development team. We used it to manage source. The QA testers used VSS to annotate modules that passed or failed, and management used it to track the status of projects by reading the notes.
For all my whining about VSS's sucktitude, it actually saved us more than cursed us. The occasional crash or weirdness was worth the end result. And I KNOW there was no way we could have gotten projects out the door without it.
When I started my business, I began using VSS to manage my own one-developer project, and rapidly became disgusted at how little it returned for my devotion. I'd forgotten we had a guy in our team who spent 1/4 of his time as the VSS administrator. A lot of the features I remembered liking in the 6-person environment simply didn't apply here: I rarely forked a project, and almost never rolled anything back entirely. "Checking out" a module was silly since I was the only guy here, and I had no QA team or managers.
I threw it out and developed my own mechanism, using Office, WinZip, and some batch files. Two years ago I ditched the batch files and started using SyncBack.
Granted VSS is a pig, and the version we used was an earlier one. I *know* versioning tools have evolved since then. If I had some spare time I would love to evaluate the latest crop of tools (one of my favorite pasttimes: downloading cool new stuff) and actually learn what I am missing.
I am NOT saying "these packages suck, my system wins". I'm simply saying that in my case
some custom-built tools fit my workflow better than what I've seen so far.
Anyway, thanks for taking the time to respond. I appreciate your patience with me.