>>Has anyone used Visual SourceSafe with Visual FoxPro 5.0? I just wanted to get an idea of how effective you felt it was. How well it integrated with FoxPro. Sorry if this may seem off topic.
>
>We've had a lot of problems even with simple PRG files - We make a change and check it back in, but the changes aren't kept. And we were working with the simplest approach - one copy on one computer - since we work off-site and just use the 'corporate' computer for a central repository.
>
>Another problem was files that VSS swore were checked out, but wouldn't check back in.

I've also seen this behavior, Barbara. We also use Stonefield's Database Toolkit and kept our DBC and all the SDT meta tables in VSS. Whenever we made a structure change and checked it in, VSS seemed to corrupt our DBC or meta tables. Not always, but enough to be aggrivating. Then we discovered a VSS configuration option to always create a new version when checking in an unchanged file. When we selected this option, we have never had another problem with corruptions or our changes not sticking. I know this doesn't make sense, but it worked for us. Go figure.

Thom, VSS is critical for us since we have multiple developers in different parts of the country accessing the same code base. However, we don't use the VFP-VSS integration. It was too much of a pain to set up. We just use the VSS client to check out and check in our files and then edit them normally in VFP. One last note, a good safety measure is to configure VSS to mark non-checked out files in a project as read-only. This will prevent you from accidentally editing a file without checking it out first and then wondering later why your changes disappeared. If you do this, though, be sure to temporarily remove the read-only flag from all your files when you build an .app or and .exe.