>> in fact I have put a desire in UT Wish for an EXECBINARY(Blob)
>
>You could, of course, create your own function. Just copy the blob to a file and "DO" it.
>
>I know there is overhead with creating a file, but if the VFP team gave us this function, I believe that is how they would handle it. Even the EXECSCRIPT function creates a temp file.

copy overhead it is the second problem, the fact is that: VFP files == insecurity

Doesn't exist any way of copying into a file with exclusive access a Blob/memo
and to execute it with a DO command; a small interval time exists where the file is free;
a good hacker can
- capture the API FCLOSE event
- to put to sleep VFP,
- to modify it ;
to wake up again VFP that performs confident a different thing.


To do this inside the memory of the VFP process it is very more difficulty
because it needs to hypnotize the OS Kernel.