David,

Thanks for the response.

This command is being incorporated into a much larger system for the purposes of speed; many slightly different versions of the code will be submitted in succession, represented by a long string of text that is modified each time. Since it's true that all it does is store to a temp file and run it, do you think this is any faster then just FILETOSTR() followed by 'DO SomeCode.prg' ? I was hoping it could all be done in memory...

Irv.

>To add to what Sergey said, (ie the code is executed as a separated .prg (.fxp really) in a temp directory)...
>All your local variables will be out of scope, so any variables you require should be PRIVATE. If you need a reference to thisform or this etc you'll need to declare private vars to reference them. In addition any resources that may be in your .exe at run-time, like .bmps etc, won't be visible to the .fxp
>HTH
>
>
>>Sergey,
>>
>>That's it! Much thanks...
>>
>>>Irv,
>>>
>>>Check ExecScript() function.
>>>
>>>>
>>>>Is there a way to 'DO' the contents of a memory variable, which could contain many lines of code? Similar to a 'DO' for a PRG file, but this set of commands would exist only in memory?
>>>>