>>>See http://stackoverflow.com/questions/132520/good-excuses-not-to-use-version-control and http://girldeveloper.com/waxing-dev/three-great-reasons-why-lonely-developers-need-source-control
>>>
>>>>I can clearly see the need for version control in a multi developer environment.
>>>>
>>>>But in a single developer environment, does it really provide much value?
>>
>>I was solo developing for 10 years before source control was even an option so I developed a lot of practices to avoid most of the pitfalls that were mentioned. When I've evaluated source control, the cost to benefit ratio just wasn't there. However I've had to fix a massive project that was multi-developed with out source control and boy was that a nightmare. I basically ended up writing something that was almost a reverse source control program.
>>
>>Things like looking back and finding earlier versions of my code are really a non-issue, when it comes up (which is actually very rare) I know where to find what I need. (I have tons of dated backups.)
>>
>>However, I develop code in 2 locations and my biggest headache is keeping the 2 locations fully in sync.
>>
>>Can Vault or TortoiseSVN help me in this situation. Which would be better? Are they secure?
>
>There are online repository services available for Subversion, I believe.

They both have some form of http access available. It looks like Subversion is limited to Apache servers. I currently have a DNN site hosted externally and an SBS 2003 server. Not sure if I can use either one of those for this.