The guy really can't win, can he...

When he says "BUG" in the thread title (some) people jump all over him for reasons unknown but consistent.

When he carefully avoids the word "BUG" in a thread title he is told that he is saying it is a bug anyway!

Another thing that I might as well clear up while I'm here...
In another thread you repled 'all you have to do is SetFocus to the grid in init' and I asked if this was documented or a workaround or what and you said it didn't matter to you. Well, it DOES MATTER, a whole lot, to other readers. If it's a documented thing then they know they can rely on finding it there should the situation arise, BUT if it's a workaround then they may want to 'file it away', possibly in some list they keep or possibly in a UT folder or possibly in the UT 'Favorites' list or possibly just as a mental note or possibly...
In other words, your reply was curt and far less helpful than it should have been.

Jim

>Fabio,
>
>>Set true or false not change.
>>
>>Before writing, you would have to verify if what you say it is correct.
>
>I did verify it Fabio. When turned on it adds a chr(26) to the end of the file when the file is saved. Please get out your favorite hex file editor to verify this for yourself.
>
>>I have said that it is a bug on my Message ?
>
>It doesn't matter, I was just letting you know it is not a bug for VFP to respect this EOF character.
>
>If you need to get the EOF character into a string constant all you have to do is use chr(26) to put it there.
>
>>I say that VFP not support EOF() char into the code.
>
>which in general for your posts means you consider it a bug.