>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

That's all correct as far as I know, but things seem to be different when it comes to SETs like PATH and CLASSLIB. These do not appear to be 'available', yet any changes you make to them appear to take effect throughout the running EXE.
At least that's how I've interpreted some observations in my code executing in scripts.

cheers


>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?
>>>>