>If the procedure throws an error and transfers control to
>an ON ERROR routine, then the only variables availble that
>DISPLAY MEMORY sees are those in scope in the ON ERROR routine.

Yup, but somehow the debugger can manage it. Perhaps a way to at least
hook into that if running under the IDE ?
Brute force with sendkeys should work...

regards

thomas