Hi John

>Long time no hear!

Nowadays I'm more lurking than anything else, but I'm still here.

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

I just downloaded Thor and intellisense today to evaluate whether it suits my needs. However, it was way too slow. Running SET COVERAGE TO log.txt revealed where the time was going to: Compiling the expressions passed to EXECSCRIPT(). From a tool that is so feature rich, the design suprised me. It can be made so much faster than it currently is.

Walter,