Capturing Procedure Names in Run-Time Error Messages

[Guest]

Hi,

Is there a way - object property - which you can query in VBA to get the
name of the procedure that is running when the error occurred. I can see
that you can get the GUID. I want the friendly name if it exists.

Thanks.

 

[Rick Brandt]

Hi,

Is there a way - object property - which you can query in VBA to get
the name of the procedure that is running when the error occurred. I
can see that you can get the GUID. I want the friendly name if it
exists.

Thanks.

No. You have to pass that to your error handler yourself.

 

[Dirk Goldgar]

Hi,

Is there a way - object property - which you can query in VBA to get
the name of the procedure that is running when the error occurred. I
can see that you can get the GUID. I want the friendly name if it
exists.

No, unfortunately. You can hard-code it, or maintain your own call
stack, but there's no way I know of to get it from Access/VBA directly.

 

[Allen Browne]

Rick and Dirk are correct.

Suggestions:
1. Create a generic error handling function, and call it from each
procedure.

2. Consider logging the errors. Users can't tell you exactly what happened
where. There's an example here:
Error Handling in VBA
at:
http://allenbrowne.com/ser-23a.html

3. Get the MZTools utility for VBA from mztools.com. With a mouse-click it
drops into any procedure your customized error handling code, including the
procedure name.

4. Don't use Me.Module.Name to pass the name of your module. It fails in an
MDE.