You beat me to it ... we've already suggested an ON ERROR statement to Ruud and I know for a fact he's seen it - so the bug is (was) in his ear ... but all this talk of pre-parsing, etc makes me a little nervous ... seems a bit overkill no ?

A statement like this should cover this off:

ON ERROR statement

eg:

ON ERROR GOTO "ABORT"
ON ERROR GOSUB "ABORT"
ON ERROR ABORT()

To keep on going :

ON ERROR RESUME

To toggle this feature on/off:

ON ERROR 0 ; it's off
ON ERROR GOTO ABORT ; it's back on

You get the picture, basically a re-hash of the VB documentation ... the power of this approach comes from the fact that statement can be any old statement you want ... so this could work in Howards' situation and probably just about any other ...

Another idea (off-topic) was to build a feature that trapped a user hitting (^C) or killing a (logon) script ... something like this:

ON BREAK statement

This would be very handy (I think) ... would allow one to properly trap (and cleanup) one's script prior to exiting .. maybe even allow one to cancel the pending abort ...

-Shawn