>Does anyone know why an FGETS() function would stop at a CHR(26) value of HEX '1A' rather than a CHR(13) Hex '0D' Carriage Return as it is documented?
>

CHR(26) is interpreted as a text file EOF marker.

>
>I am losing data on a low-level file read when reading record by record because of garbage data being sent to us in a file. We have been stripping out CHR(0) values to clean up the data, but this is a new piece of garbage being supplied to us to check for.
>
>TIA