>Walter,
>
>Long time no hear!
>
>Thanks for reminding that Execscript can be quite slow because it caches then "compiles" your prg script every time. Whereas Eval() or even & Macro Substitution are almost as quick as "compiled" code after the initial hit to get the interpreter loaded. If it's possible to express your code in a single line, Eval() is extremely quick. Of course if you have a busy tight loop I agree with your tactic of pre-compiling as much as possible though it does create hack opportunities if you're DOing writeable prgs that exist outside your app...

Do this:

execscript("?sys(16,1)"+0h0d+"set step on"+0h0d+"return")

Do it any number of times. You'll see that it writes a .rmp file containing just your command (no you can't open it but check the size), and a .fxp of the same file. Then it deletes both. So it's a strtofile(), compile, do, erase two files. Every time. You can check your temp folder while it's in the debugger.

Alternately, you can just

execscript("?sys(16,1)")

and keep filemon or process explorer active. You get a different couple of files each time.