After looking at the code, I guess I've never encountered it because the FGETS() is only called when you try to create a binary file from a text file generated by SCCTEXT. I've never done that, as I only use SCCTEXT for generating the text files to show differences.

Seeing as how this program is used for FoxPro's SourceSafe integration, I'm suprised Microsoft didn't fix it for SP3. I guess they must have just missed it.

Thanks for the heads up.

>>Yeah, I guess it does. I didn't know that was there. One problem with it, though, is that it doesn't put the methods in alphabetical order. I ran into that problem because for some reason VFP rearranged the order of the methods in the memo field so BC was showing massive changes between the two forms when there really wasn't.
>>
>>Thanks,
>>
>>Michelle
>>
>>>Doesn't SCCTEXT.PRG do this already? It converts forms, labels, menus, reports and vcxs to text output. It should be in your VFP directory.
>
>To ALL:
>
>Be warned that SCCTEXT.PRG has calls to FGETS that are illegal under VFP6 SP3. You need to change the # of bytes from 65000 to 8192 in 4 places.