>>Well, there's not a general topic for source code control, so I'll just ask this general question here . . . I'm trying to evaluate systems (VSS, subversion, Vault, etc.) and I know that one of the issues is VFP's table-based source code. I'm wondering how people deal with that effectively? I'm also just looking for general recommendations on which system might be the best.
>>
>
>VFP includes a program that converts those to separate text files that can be used for diffs. This gets called automatically from the VFP Project Manager when using VSS, but you may be able to use it with other systems. An updated version of the program is on VFPX:
>
>http://vfpx.codeplex.com/Wiki/View.aspx?title=Alternate%20SCCText
>
>There is also a separate project to integrate VFP with Subversion:
>
>http://vfpx.codeplex.com/Wiki/View.aspx?title=SubFox

SubFox is a ways off and so I don't think I can really include that in the list of candidates. There do seem to be some ways to work with Subversion by using SCCText or an alternate (there are a few). I have heard of problems with VSS - a lot of people using it with VFP don't seem to be too enthralled with it. Seems like, overall, people like Subversion better. Thanks for your reply.