>>Go into SCCTEXT.PRG and change the constant SCC_FORM_SUPPORT to 2 rather than 1, and try running it. Works for me.
>
>I did this (using VFP6) and the program causes an error on the following line
>

>this.ValidVersion(fgets(this.iHandle, 65000))
>

>
>This statement results in the error handler being called and it displays the message
>

>Error #11 in writetablefile(10): Function argument value, type, or count is invalid.
>

>
>I broke this code apart so I could see what the offending portion actually was. For some reason VFP6 was complaining about the second parameter to FGETS(). I removed the 65000 parameter and the FGETS() call worked. Now the VFP6 help file says you can specify a numeric second parameter to FGETS() as the maximum number of characters to return but for some reason my copy of VFP6 didn't like this numeric second parameter. I am running VFP6 SP4.
>
>I just checked the knowledge base on our MSDN and found that SP4 had changed the maximum value for the second numeric parameter to 8192 because of a previously discovered bug. I changed all the 65000 parameters in the FGETS() calls (about 4 of them) to 8192 and the program worked. Nothing like the original Microsoft code being broken by its own bugs.

Yeah, and it worked for me because I'd already modified my SCCTEXT in VFP6 to handle the bug, and it's corrected in 7.