Error Handling - Outputting Call Stack

[ions]

Can the Err ojbect give me the current Call Stack or do i have to code this myself if I want it to appear in my Error Log / Error Message?

Thank you

 

[the_net_2.0]

what do you mean by CALL STACK??

err will only give you methods and properties associated with the error that's in the object at the time you request it.

 

[ions]

Maybe the Err object is misleading.

What I want is an Array that holds the Procedure Call Stack. Is there an object in VBA that holds that info? The Call Stack is available in the IDE but I want to access it in code.

Thanks

 

[the_net_2.0]

What I want is an Array that holds the Procedure Call Stack. Is there an object in VBA that holds that info?

i'm pretty sure there's not. but I have to ask, why are you looking at it? or why do you 'want' to look at it and track it?

 

[ions]

I wanted to track it so when I am offsite it would help me resolve the bug.

This seems to be what I was looking for:

http://www.everythingaccess.com/vbwatchdog.htm#moreinfo

 

[Banana]

A possible DIY example is to set up your error handler to allow errors to bubble upward and gather the information. Example:

Public Sub TryIt()
On Error GoTo Error_Handler

  A

Exit_Procedure:
  On Error Resume Next
  Exit Sub
Error_Handler:
  Select Case Err.Number
    Case vbObjectError
      MsgBox Err.Description, vbOKOnly + vbExclamation
    Case Else
      MsgBox Err.Number & ", " & Err.Description
  End Select
  Resume Exit_Procedure
  Resume
End Sub

Public Sub A()
On Error GoTo Error_Handler

  B

Exit_Procedure:
  On Error Resume Next
  Exit Sub
Error_Handler:
  Select Case Err.Number
    Case vbObjectError
      Err.Raise vbObjectError, "MyClass", "In Procedure A:" & vbNewLine & Err.Description, Err.HelpFile, Err.HelpContext
    Case Else
      MsgBox Err.Number & ", " & Err.Description
  End Select
  Resume Exit_Procedure
  Resume
End Sub

Public Sub B()
On Error GoTo Error_Handler

  C

Exit_Procedure:
  On Error Resume Next
  Exit Sub
Error_Handler:
  Select Case Err.Number
    Case vbObjectError
      Err.Raise vbObjectError, "MyClass", "In Procedure B:" & vbNewLine & Err.Description, Err.HelpFile, Err.HelpContext
    Case Else
      MsgBox Err.Number & ", " & Err.Description
  End Select
  Resume Exit_Procedure
  Resume
End Sub

Public Sub C()
On Error GoTo Error_Handler

  Debug.Print 1 / 0

Exit_Procedure:
  On Error Resume Next
  Exit Sub
Error_Handler:
  Select Case Err.Number
    Case Else
      Err.Raise vbObjectError, "MyClass", "In Procedure C:" & vbNewLine & Err.Number & ": " & Err.Description, Err.HelpFile, Err.HelpContext
  End Select
  Resume Exit_Procedure
  Resume
End Sub

The resulting error message would be:

In Procedure A:
In Procedure B:
In Procedure C:
11: Division by zero

You'd use MZ-Tools to automate the building of error handler.

Not as full-featured as this vbWatchDog, but YMMV.

 

[ions]

Hi Banana,

Thanks for the code. I am a little tired at the moment but will take a look at your solution when I am more fresh.

Luke Chung from FMS also has a code solution at

http://www.fmsinc.com/tpapers/vbacode/debug.asp#AdvancesErrorHandling

I am trying to avoid a code solution because am I want to apply this on an already built application.