Since you can't catch those via the program concerned, we merely put a program in the ON.ABORT paragraph to stop the users being dropped to the TCL prompt (where even more damage could be accidently be done). An @ABORT.CODE value of 3 is suppose to indicate an internal and/or fatal error, but we've found thing condition rarely gets raised. Hence, we using automatically logout the user we a message telling them to contact the helpdesk immediately.
David,
we were going to update our existing ON.ABORT paragraph, but not only is the error not caught by ON ERROR, the user doesn't abort!
I agree about allowing these to be catchable -- even if there isn't an obvious graceful exit, at lease I could stop this and other users working until the error is fixed.
Craig ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
