We are still using SourceSafe (VSS) + SourceOffSite, but we'll eventually switch to something else. I thought I heard somewhere that Vault is free for a single developer, so if it's just you, you could look there. Vault is similar in philosophy to VSS. I don't think VFP is officially supported by SourceGear, but some have evidently managed to get it working. Microsoft TFS is similar as well, but has additional features, like work item (bug) tracking. I have used it with VFPX, and I can confirm it integrates with VFP, once you get everything set up, like installing the MSSCCI provider. If you don't get it with MSDN, it's big bucks. If you use either of those, make sure you grab SCCTextX from VFPX. Here's an article a guy from SourceGear wrote on the subject:

http://www.simple-talk.com/sql/sql-tools/life-after-retirement-replacing-visual-sourcesafe/

I've never used Subversion or Git. My understanding is that they are different animals than VSS, but at least a few are using Subversion with VFP, and there is a project for it in VFPX. If you're looking for free and not tied to a specific philosophy, that might be a good place to start.

>Craig,
>
>If one is "starting out fresh", as I am, with implementing version control, which system would you recommend. I have read on here where people are successfully integrating Vault with VFP... but Vault is not free. I have also read that Git is considered to be a "DVCS", distributed version control system, whereas Subversion uses a "traditional, centralized model". I also just read that Vault now integrates with a SQL Server version control system from RedGate... something that would be very important in this environment.
>
>Honestly, my experience is minimal in this area... a little bit of exposure to Sourcesafe. But I gave it up because of what I perceived to be its limitations in handling vcx's, scx's... something that has been addressed here, and something that I will obviously have to revisit.
>
>
>>Because forms, reports, class libraries, and other files are not stored as text, any source control program will have problems tracking changes to them. VFP ships with SCCText.prg that creates a text version of those files to ease the SCC issue.
>>
>>However, I would not consider Source Safe at this time. It has known issues and has been discontinued by Microsoft. Many people have turned to Subversion or Git, both free or to Microsoft's TFS.
>>
>>>Hi Friends,
>>>
>>>The sourcesafe 6 works well with Visual FoxPro? It tracks changes in forms?
>>>
>>>Thanks in advance
>>>
>>>Dionísio