VBA Error logging 2

[VicM]

Hi,

I'm trying to polish my MSAccess VBA code by introducing error logging. I discovered a way to log the errors to an external file. The example showed how to pass the error message to a Sub which logs the info to a file. Obviously I can also pass the error number as well if I choose. The following is the code I found which is called from each 'On Error' handler section of the Sub or Function.

Sub LogError(msg As String)
    Dim fileName As String, fileNo As Integer
    fileNo = FreeFile [COLOR=#4E9A06]'Get first free file number[/color]
    fileName = "f:\DBMS\error_log.txt"
    Open fileName For Append As #fileNo
    Print #fileNo, Now & ":" & msg
    Close #fileNo
End Sub

But I'm at a loss as to how to pass to the error log, the source of the error. By that I mean which Sub or Function, from which form/report/module caused the error.

Is there a way to extract the Sub/Function/Module name source so I can pass it to the logging Sub?

Thanks,
Vic

 

[Andrzejek]

from which form" - you can do that easily:

Private Sub btnTest_Click()
    Call LogError("My Message", [blue]Me[/blue])
End Sub

Sub LogError(msg As String, [blue]frm As Form[/blue])

MsgBox frm.Name
MsgBox frm.ActiveControl.Name
...

You may need to declare [tt]frm As MSAccess.Form[/tt] or something like that.

As far as "Sub/Function/Module name source " - I don't know how to do that, unless you would pass another specific (hard-coded) parameter to [tt]LogError[/tt]


---- Andy

There is a great need for a sarcasm font.

 

[VicM]

Thanks Andy. That's a start.
Appreciate the suggestion.

Vic

 

[MajP]

No generic way to do it, but since you have to call the error log procedure you just pass it in. Just copy and paste the code into your errorhandler and change the sub routine name.

..... in your error handler paste the following and change the routine name

dim msg as string
dim rtnName as string
rtnName = "Type Your Routine Name Here"
msg = err.number & ": " & Err.description & " in routine " & rtnName  & " on form/report: " & me.name
Call LogError(msg)

 

[Andrzejek]

You may also explore adding line numbers to your VBA code and use erl


---- Andy

There is a great need for a sarcasm font.

 

[strongm]

You might look to look at vbWatchdog here

https://www.everythingaccess.com/downloads.asp

 

[VicM]

MajP

I like the way you think. I was doing something along those lines at the class level initially.
I set a Private Const at the class level with the Class/Module name. Then when I called the ErrorLog routine, I passed the Const as one of the arguments. I was considering doing exactly what you suggested at the Sub/Function level as well.

It's not the most elegant solution, but it will work and be helpful to track where an error occurs.
So a star for you and one for Andy who got me thinking along those lines as well.

Thanks folks,

Vic