Hi Joe,
You may want to look at the date stamp of your prg's and other individual files, and then I saw a few days ago a tool called "database comparer" or something like that in the UT's login page's news items which might be useful to compare class libs and project files, which are basically dbf's with their file extensions changed to vcx, pjx, etc.
Another option might be to do a filetostr() of each of these files and compare them as strings in a prg. Won't give you punctual differences, but it might be a good start.
Alex
>We have MS SourceSafe, but do not think it is adequate to do what we are looking for.
>
>We would like to take an old version of a VFP Project, and a new version of a VFP Project (after we have made many code changes) and use some sort of tool that compares them and explains the differences in the Programs, Forms, Classes, etc.
>
>There must be something like this that exists? What is best?
>
>This happens often... old version of our software works fine with one particular function, 4 coders make lots of changes, bug isnt noticed till months later, new version's particular function no longer works, hard to find what we changed that specifically hosed that original particular function.
>
>If I could better compare projects, and get a detailed listing of what is different, I could better resolve these issue's I am sure.
>
>THANKS FOR ANY SUGGESTIONS!
Low-carb diet not working? Try the Low-food diet instead!