<div>
I think I answered my own question after some research... &nbsp;<br />
<br />
As Shauli said, there is no easy way to access the callstack at runtime. &nbsp;Dan Fergus offers a workaround using dgbhelp.dll in his article Get Debug Info From Production App -- <a href="http://www.ftponline.com/vsm/2002_05/magazine/columns/blackbelt/default_pf.aspx" rel="ugc">http://www.ftponline.com/vsm/2002_05/magazine/columns/blackbelt/default_pf.aspx</a>&nbsp;(requires registration).<br />
<br />
Shauli, I'll reward you the points
</div>


I think I answered my own question after some research...  

As Shauli said, there is no easy way to access the callstack at runtime.  Dan Fergus offers a workaround using dgbhelp.dll in his article Get Debug Info From Production App -- http://www.ftponline.com/vsm/2002_05/magazine/columns/blackbelt/default_pf.aspx [http://www.ftponline.com/vsm/2002_05/magazine/columns/blackbelt/default_pf.aspx] (requires registration).

Shauli, I'll reward you the points

<div>
<div class="content wysiwyg-content">
Is there a way to access the VB call stack at run-time. Basically I want a procedure to be able to determine the name of the procedure that called it
</div>
</div>


Is there a way to access the VB call stack at run-time. Basically I want a procedure to be able to determine the name of the procedure that called it

Call Stack

Visual Basic is Microsoft’s event-driven programming language and integrated development environment (IDE) for its Component Object Model (COM) programming model. It is relatively easy to learn and use because of its graphical development features and BASIC heritage. It has been replaced with VB.NET, and is very similar to VBA (Visual Basic for Applications), the programming language for the Microsoft Office product line.