[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