Mark,
This would have broken with SP3, the change to a maximum of 8192 was implemented then. Check out MS KB article Q221747.

BTW, FGets always stopped at a carriage return so I'm not sure what the problem is. FRead would have been my choice in this scenario.

>Take a look at the SP4 update notes for VFP. How many people have legacy VFP code out there, before the FileToStr function came along, that _knows_ it's going to reading an entire textblob file of some arbitrary length less than 32K characters and is simply coded as:
>
>cMyStr=FGets(hFile,32767)
>... Basically the equivalent functionality of FileToStr before it came along.
>
>That apparently will now be broken. From the SP4 info:
>
>FGETS function update
>
>A minor behavior change was necessary for the FGETS() function related to Knowledge Base article.
>
>The optional nBytes parameter now has a maximum value of 8192. By definition, FGETS() only returns bytes up to a carriage return if one is encountered before the parameter value is reached.