I now believe this is a foxbin2prg issue, because the problem with checkin comments longer than 40-50 chars only occurs on a binary file that is run thru foxbin2prg. A .prg file does not have the problem.

Why in the world would foxbin2prg work perfectly under all circumstances unless a checkin comments is a certain length? Then it failes and loses data. Multiple checkins, every feature of VSS/SoSis fine except for this.

What does foxbin2prg have to do with checkin comments? Does it read them in any way?





>>All permissions are correct and I can convert the file fine. It happens with any form or classlib. It does not happen if I check in/out files directly thru SoS or VSS.. IOW it is a consistant behaviour. I have never seen this before with the VFP IDE and VSS/SoS, and I am at a loss to explain it. I am also at a loss gto explain why foxbin2prg then wipes the changes to the form/classlib.
>>
>
>Hi Tuvia:
>
>If you are using the integration between VFP projects and SoS/VSS, then I suspect that the bidirectional convertion of FoxBin2Prg is not supported by those tools, so if this is the case, I see 2 possible solutions:
>
>1) Don't use this integration: Use SoS interface externally, convert the files to binary/text from Windows File Manager and checkin into SoS as any other file, this way no strange things should occur
>
>2) Disable bidirectional support in FoxBin2Prg: In this case you can use the integration with SoS/VSS the same way as with SccText(X), so no problems should occur in this "compatibility mode", but you loose the best functionallity of FoxBin2Prg (regeneration of binaries from text) and you couldn't "merge" between branches.
>
>I think that option 1 is the best way.
>
>I don't know if we could talk about a 3rd.option, that is: Contact SoS support to see what can be done in this case, because this is clearly something out of FoxBin2Prg.
>
>Talking about the "access denied" problem, I remember that SourceSafe make the file "read only" when checked in. Can't be this the problem with SoS? May be there is a way to not make files "read only" in the SoS configuration? (VSS can disable the "read only" thing)
>
>May be I can add some specific checking of the read only attribute in FoxBin2Prg to notify it.
>
>
>Best Regards!