MsgBox "Error in " & ProcName & vbNewLine & _īonus suggestion: roll your own stack trace. 'Show MsgBox so error does not go unreported ' Print #nUnit, " " & ErrNum & ", " & ErrorMsg Open App.Path & App.ExeName & ".log" For Append As nUnit ' You will need to choose another directory if this is not possible ' Everything was working fine since yesterday, but today in my timezone we started daylight time saving (added one hour) And Log was flooded with Errors like this. Viewed 61 times 0 Ive got serious issue with otrs 6. ' This assumes write access to the directory containing the program ' OTRS 6: Errors flooding log file when daylight saving time showed up. m command at the debugger prompt displays a information about the currently loaded modules including module name, version and date. Figure 6: The results of the 'dds' debugger command. Sub LogError(ProcName$, ErrNum&, ErrorMsg$) As shown in Figure 6, you can now fill in the stack trace portion of the Abend Log File worksheet. Sub MySub()Ĭall LogError("MySub", Err, Error$) ' passes name of current routine '
Health warning - I've just typed this straight in without testing it ( air code). You also need a general routine that logs error details to a file, a little bit like this below. (BTW in VB6 they are called errors not exceptions.) The free tool MZTools is excellent - it can automatically insert the On Error Goto and an error handler which includes the name of the current routine. You need error handlers, using On Error Goto, so that you can execute your own code when an error occurs.
0 kommentar(er)
