Well the stack trace is doing what it suppose to do. This is were debugging
comes in. If you downloaded the .NET framework SDK then you should have a
GUI version of the CLR debugger. Look for it in the GuiDebug folder in your
SDK install directory. Then use it to set a breakpoint and step through
your code until you break at the line causing the error.
BTW, I am assuming you are NOT using VS.NET, if you are, should have already
went through this process
"Wayne Wengert" <wa***************@wengert.com> wrote in message
news:eS**************@TK2MSFTNGP10.phx.gbl...
When I get runtime errors the stack trace includes a pointer to a specific
line in the code but that line often seems to point to the line that makes
a
call to a subroutine while the error is somewhere in the subroutine? Is
there a way to get the actually line nbr that caused the error?
Wayne