Get name of funcion when error ocurr...

[VBSHAR]

Hello all!

How to i cam automatic get the original name of a function when an error occurs, and how to i cam handle one global procedure to error treatment?

see this code:

Private Sub MyFunction()
On Error GoTo GlobalErrorTreat:
 
Dim x As Integer
Dim a As String
Dim r As Boolean
    a = "a"
    x = 1
    r = a * x ' this generate an error
    MsgBox r
End Sub
 
' in a global module or class
On Error GoTo GlobalErrorTreat:
MsgBox "This error ocurr in : " & FunctionName
'how to get FunctionName is my problem...
Resume Next

Thanks!

[crptcblade]

Well, there is no automatic way to get the function name, you'll need to keep track yourself.

Also, there is no such thing as global error handling in VB, you need to set error traps in each sub/function.

[ober0330]

This will solve all of your error handling needs:

Go download this: http://www.mztools.com/

Put this:

On Error GoTo {PROCEDURE_NAME}_Error
 
    {PROCEDURE_BODY}
 
   On Error GoTo 0
   Exit {PROCEDURE_TYPE}
 
{PROCEDURE_NAME}_Error:
 
    Logerror err.Number, err.Description, err.Source, False, "{PROCEDURE_NAME} of {MODULE_TYPE} {MODULE_NAME}"

In the "Error Handler" tab of the options.

Then add this module to your project:

[ober0330]

OH, and in case anyone else is interested, you can click one button to add either just the error handler to your sub/function or you can click another button to add the error handler and a comment block to the sub/function.

The module simply takes all the information and writes it to "error.log" in the current directory.

OH, and when you use mztools, it will automatically fill in the procedure name and module name for you

edit: I add this to all my projects and it saves me a TON of time.

[DeadEyes]

When I'm using classes I generally have a const for the class name
and a const in each method with it's name and add these to the err.description

Err.Description = CLASS_NAME & "." & PROCEDURE_NAME & ":" Err.Description

[Wokawidget]

Here is a small demo I use for error handling.
It records exactly which procedures the error ran through so debug is made very easy. If you force an "error" ie, "user not found" then a different style of message is displayed.

To test both types of error message just change which error line is remarked out....

You should ONLY EVER DISPLAY errors under click events or such like and never through custom subs/functions that u have written yourself.

Hope this demo is useful.

I have stripped this out of an ErrorHandling DLL I have. The full version also saves to a log file of your choice when you display the error, also it saves it to the DB....if a user has an error, then u will never have the situation where they say, I can't remember how I got it, coz you will have a 100% log of it all

Woka