>
>Visual FoxPro even allows you to save files with these special EOF characters if they are required. Look at the properties dialog from a MODI FILE edit window.
>
>
>Set true or false not change.
>
>Before writing, you would have to verify if what you say it is correct.
>
>
>So it's not a Visual FoxPro bug, you'll have to go all the way back to the guys that invented ASCII to report this one. *s*
>
>
>I have said that it is a bug on my Message ?
>
>I say that VFP not support EOF() char into the code.

It supports it, just as it did fifteen years ago, and in the sense that it respects EOF marker: it stops reading the code beyond that byte. So you've found it, it's just that it doesn't do what you expect.

On some systems (read: older versions of DOS, maybe some UNIX/Xenix editors etc), it was possible that the length of the file is lost, and the file is rounded to the boundary of the whole cluster on disk. In that case, the garbage beyond the actual end of the file becomes a part of the file. Making software respect the EOF marker made a lot of sense in such cases. The decision to do so originates probably in dBase II or so - and it's stayed that way. If it was changed today, it would probably break some code which worked happily for 15 years or more, because it would start finding this garbage and producing syntax errors everywhere.

Keep in mind that almost all of the 80s code written in Fox can still run under VFP8, with little or no change. There's no other M$ product out there (except maybe some Fortran compilers) which can do that.