User Shum, Garry (garry.shum@ROYALBANK.COM) posted:

Content-Type: text/plain;
Content-Transfer-Encoding: 7bit

I'd like to know if it is necessary to turn off the exception handler of an
exception within its exception handler function to prevent it from being
triggered while the exception handler function is still running? I've seen
examples of exception handler functions where the exception is turned off at
the beginning of the handler function and back on at the end of the handler
function to prevent the exception from being re-triggered. However, I don't
see why this is necessary because I've never done this and my exceptions
work fine. What is the exact reason for doing that? Is it because a
triggered exception will only not be retriggered until you exit the handler
function or until you call a custom function and is therefore necessary for
those who use custom functions within their handler functions?

Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7bit

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">

< !-- |**|begin egp html banner|**| -->