[AccessD] [SPAM SUSPECT] Error Trapping

Hi Bobby,

Yes - if there was no handler in B then A would pick it up.  But this
happens when there is a handler in B.  That's the puzzle!

Dan Waters
 

-----Original Message-----
Subject: Re: [AccessD] [SPAM SUSPECT] Error Trapping

I think that the scenario that you posed happens when there is no error
handler in B.  So I think the solution is to have an error handler in every
procedure.

Bobby

-----Original Message-----
Subject: [SPAM SUSPECT] [AccessD] Error Trapping


For a long time I've seen that an error trapped in one procedure may have
actually occurred in a called procedure.  For example, if Procedure A calls
procedure B and an error occurs in B, then the error might get trapped in A,
not in B.  So my error log shows an error trapped in A, but I need to know
that it happened in B.

Is there a way to accurately know which procedure actually triggered an
error?

Thanks!
Dan Waters