>I am quite a reasonable thinker. I believe I mentioned that I did not know if foxbin2prg had access to checkin comments.
>
>Changing to one way tool and your other solutions would obviate the need for foxbin2prg. The two way capability from the IDE is why we use it. I never use non-integrated source control, it makes too much work and hassle for the developers.
>
>I can demonstrate that it is most likely not a SoS/VSS issue as follows: I can replace foxbin2prg as the converter with scctext2 and the problem goes away. IOW the only time the problem ever occurs is: the VFP IDE, binary files checkin, foxbin2prg, and comments over a certain length. IOW it ONLY happens when foxbin2prg runs.
>
>It is logical, and reasonable thinking, to presume there is a connection, especially since foxbin2prg when this error occurs incorrectly takes the .?a file and recreated the binaries, in effect overwriting all the changes to the form/class.
>
>I did not expect you to have a copy of SoS, but since VSS is pretty ubiquitous I thought you might have a copy. But really what I was hoping was that you might have an idea off the top of your head why foxbin2prg would backwards generate and wipe changes, or why it crashed in the first place.
>

Hi Tuvia:

If you campare SccText with FoxBin2Prg, then compare them in the same use case, not in different use cases.

What I mean with this:

- When you use SccText, you can only generate text files, so there is no binary regeneration and if the binary is made ReadOnly by the SCM tool, you are not affected because SccText just read it. The same should be true for FoxBin2Prg in text-only mode

- When you use FoxBin2Prg as 2-way converter, *if* your SCM tool made the binary ReadOnly, then you can get a "File access denied" when FoxBin2Prg tries to regenerate it, because can't write to it

This is why I've asked if you can check testing in "1-way" conversion, to make the comparison in the same terms.
Have you enabled the ReadOnly attribute on the SCM? (VSS have this configurable and is turned on by default) Because, if yes, you could disable it, so this should fix this problem.

I'm going to do some tests with SourceSafe to see if really support bidirectional convertions.