>Helping a site that is interested in introducing source control for a set of VFP7 and VFP9 applications.
>
>I've used a variety of source control on other non Fox developments but wondered if anyone has strong recommendations for or warning on source control systems that could be applied.
>

No correct answer possible from my POV. Guessing that the team is not on the bleeding edge of tech, I'd ask if one tool is known/used in that group, so newbies can be brought up to speed by old hands. Minimize "group" effort, as differences between tools are not so big compared to having no SCM at all.

If zero source control knowledge exists:
for not too large code bases the out-of-the-box integration of Source Safe works well enough over at least 1MB for WAN connections,
even better if coding is done on VM on site via RDP. Besides checking for file corruption the technical/speed problems for WAN access
are a thing of the past. Least amount of work/schooling needed and MUCH better than no SCM at all. I think coding SHOULD be done on a VM inside client net and whole project or VM cloned/copied if work needs to be done on disconnected dev machine - works for me ;-)
Having your "personal checkout copy" inside the VM is a nice "backup benefit" of unmerged changes.

SVN worked well enough the few times I used it, but is a tool more used in the past as today. TFS supposed to be good, but complex - use it only if one is around who knows it. Git probably the tool most in use today.

Tortoise as a GUI if you need one, as it supports multiple engines - had it installed for SVN, but used command line.