Trap which sub/func triggered the error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Good morning,

I came accross an article or entry that covered this issue and cannot find
it anymore.

I would like to know how I can trap in my error reporting message which
sub-routine, function, etc. cause the error in the first place? I tried the
err.source but this is vague and does not help identify which part of the
code is generating the error.

Thank you,

Daniel
 
Daniel said:
Good morning,

I came accross an article or entry that covered this issue and cannot
find it anymore.

I would like to know how I can trap in my error reporting message
which sub-routine, function, etc. cause the error in the first place?
I tried the err.source but this is vague and does not help identify
which part of the code is generating the error.

Thank you,

Daniel
Click to expand...

You need to identify the source yourself. There is nothing built in. My custom
error handler accepts a single text argument. Whenever I use it I add to that
argument the name of the function or sub.
 
Rick,

Thank you for the reply! That was the approach that I've taken so far but I
had hoped that there existed a simpler method/technique.

There's an item to add to the MS Access wish list?!

Thank you once again.

Daniel
 
Back
Top