Thanks for the heads up on Git. In the meantime I have downloaded a trial of Vault. I will probably try Subversion too.
Regarding Redgate, I'm not concerned about backup, I'm specifically talking about source control:
http://www.red-gate.com/products/sql-development/sql-source-control/

I'm looking at other threads by tc holzer, Hank Fay, regarding Vault / VFP integration.


>I wouldn't use Git with VFP because it's way too difficult to merge non-text source files. I know of VFP devs that are using Subversion. Keep in mind that AFIAK, it doesn't integrate into the VFP IDE, but it isn't really a problem to manage files externally in Windows Explorer so long as you remember to check out forms, reports, class libs, menus in pairs.
>
>SQL Server backup is far different that backing up source code. I would not look at a single solution for both. SQL Server backup is more like a standard disk back up, but you need an agent to handle the open SQL Server files. If you're looking for change tracking in SQL Server, Red Gate has some great tools for that.
>
>
>>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.
>>