>Run this into the Command window:
>

>* next return a correct 26
>? ASC('put here one ASCII 26 character with ALT+026')
>

>
>

>* next two are comments
>*put here one ASCII 26 character with ALT+026'
>&&put here one ASCII 26 character with ALT+026'
>

>
>

>* next RETURN  a syntax error
>EXECSCRIPT([*put here one ASCII 26 character with ALT+026'])
>

>
>Now, replay these into a PRG, and compile.
>You have a error, even if to put LitteralASCII_26 ' into to comment.
>
>CHR(26) is a special VFP token ?
>
>I cannot put LitteralASCII_26 into the UT editbox, also.

Fabio,
You're right it doesn't support. But it supports it if you do not literally input it (as with chr(0),chr(13),chr(10) and other all chars in 0..255 range). In production this doesn't cause any problems on my part (regarding to binary streams) actually even in fox2x days I've written and executed .bin code on the fly (why would I do that is my problem:).

EXECSCRIPT([*put here one ASCII 26 character with ALT+026'])
fails, but :
EXECSCRIPT([*]+chr(26))
succeeds.

In foxbase days however chr(141) was really a problem that I could never resolve (and unfortunately it was the ASCII code of one Turkish char).
Cetin