General information
Category:
Coding, syntax & commands
>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
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only