>Gerry, all my bugs are found into my application.
>
>If a my message does not interest to you, ignores it.
>
>On this specific:
>

>* On VFP you can define a binary stream into the code ?
>* like
>x = 0hffC50910cd....
>

>
>AFAIK, No.
>
>Then you can define it with a string,
>obviously CHR(0),CHR(10),CHR(13) is not allowed,
>but CHR(26) ( EOF() tag ) it is not immediate
>because VFP have a option for not put EOF(),
>then it can ignore EOF().

You misunderstood this - it can save the files with or without the EOF marker in the end, which is for compatibility with whatever other software the user is using, which may need the EOF marker to work properly. But if the EOF marker is found in the source, VFP will respect it, not ignore it.

>- that an operation on command works,
>while in programs it not works,
>and into EXECSCRIP() not works
>
>Then a question is :
>EXECSCRIPT() built a temporary file for exec the script ?

I think the answer to this is yes. Now whether the file actually exists on disk or not, that's another question. In the debugger, you can see that the name of the procedure currently executing during an execscript is generated by sys(2015).