Hi Bill,

In our case, we have to leave VFP disconnected from SourceSafe because of Configuration Management issues. As the team leader, the ultimate quality of the code rests with me.

The way I have chosen to monitor the changes to our binary files has been to take the SCX's and such and run them through _SCCTEXT (i.e. DO (_SCCTEXT) WITH "MyForm.scx") This creates a .SCA/.FRA/etc. file which is a text representation of the form. Then I use SourceSafe's diff function to see the differences. _SCCTEXT is the program that VFP uses to parse the files prior to checking them into SourceSafe (when you use it in integrated mode). You are just doing manually what the automation would have done for you.

Markus Egger has written a utility that goes through you working directory and creates the text files for any files you have checked out. This might help you. I think it's called SourceSafe Boost.

I'm working on a personal utility that will spin through SourceSafe and generate historic text files for all my forms and reports.

What you're describing, a FoxPro specific diff tool, would seem to be a pretty straight forward exercise, using the _SCCTEXT engine. But, since by definition, you need "versions" of a program to do this, you'd probably be using SourceSafe anyway.

Hope this helps.

Marty