This is probably totally unrelated, but we've had problems with screens/classes showing up as different, even though there weren't really any changes. The problem stemmed from the screen/class including a .H file, and different people had the same version of the .H file, but had different physical timestamps on the .H file. I believe the default for SourceSafe is to put the current date on a file when it does a Get. Therefore, different people will have different timestamps on their .H files. Also, if you are on NT, the timestamp on all of your files will either gain or lose an hour during the Daylight Savings Time switch-overs. When FoxPro rebuilds, it must assume the file is different since there is a different date from the last time it rebuilt, and the form/class is recompiled.

We now make sure that all of our SourceSafe users have the Local File Timestamp option in SourceSafe set to the Modification time of the file. Also, during the Daylight Savings Time switch-overs, we delete the .H files off our local machines and re-Get them from SourceSafe to make sure they have the correct timestamp.

>Help! I'm trying to use Visual SourceSafe (6.0) and integrate it with VFP (6.0). (I've upgraded to Visual Studio SP4 also). When I try to diff any vcx's, I get the 'Binary Files Differ' message. My understanding was that the comparision was done on the VCA's generated by SCCTEXT (I've made the changes suggested in Fox Advisor Oct 97). The Forms (sca), Reports (fra), and Menus (mna) work as advertised, just the vcx (vca) are giving me the message.
>
>Could I have missed something the setup? Or messed up something in the setup?
>
>Thanks for any help...
>
>Tom