Guys is there anything that can be done with the fact that once you start using this new version of SCCText and compare the differences to a history item, everything is different because of the order of things? Therefore trying to compare versions that were produced with the old & new SCCText is kind of useless.

Is this more of a going forward thing?

When the project is rebuilt all classes and forms etc.. are modified and marked as checked-out but text files generated by SccTextX are still read-only so on check-in I have a lot of requests to overwrite these files.
How can be solved?
Maybe you could add a flag "overwrite all"?
Or there is workaround?

Hi Amariottini, this behaviour should also show up with the original Scctext, thus it's not a bug from that newer version.
But I see your point. Will play with that problem and try to implement some additional functionality.

Yes, this is by design but maybe this could be enhanced.
By now I solved commenting out the read-only check and simply let SccTextX to overwrite any text file.
Another problem with VFP integration with source control systems is that after a rebuild of the project all forms, classes, etc.. become checked-out so I have to re-check-in all of them spending a lot of time and changing without need the version number (and growing repository). This is a very bad behavior, I know that build modify the vcx and/or vct files but the source code is not touched, so why other developers have to see them as modified? Is there any workaround for this?
There are very few informations in internet about VFP and source control systems integration so I'll appreciate any suggestions.