if I have an error handler like this

on error goto fErr
....
....

fExit:
exit sub

fErr:
msgbox err.description
resume fExit

is there a way for the msgbox to also display either the line # or the
actual vba of the line that caused the error

note, the above msgbox is for illustration purposes, the actual error
handler logs the error to a text file, that's why logging the line #
or a reference to it would be helpful

Roger wrote:
in VBA - it's been a while) that shows the line number of the line that
raised the error, but only if you use line numbers:
http://msdn.microsoft.com/en-us/libr...w1(VS.80).aspx.

Otherwise, the best you can do is check for an error after each line of
code using "on error resume next" instead of "on error goto
err_handler". This will allow you to return a different message box
title
for each line of code, allowing you to identify the guilty line:

on error resume next
blah blah blah
if err<>0 then
msgbox err.description,,"first statement"
exit sub
end if

blah blah blah2
if err<>0 then
msgbox err.description,,"2nd statement"
exit sub
end if



That's a lot of trouble to go through. For debugging, I will often use
something like this:
fExit:
exit sub

fErr:
msgbox err.description
Stop: Resume
resume fExit

commenting out the line when I am finished debugging. Resume, of course,
causes the same line that raised the error to be executed again.
--
HTH,
Bob Barrows

Roger wrote:
Oh, and check out this thread that I found when searching for "vba erl
property" after posting my previous reply (I was curious to see if it
existed in VBA):
http://stackoverflow.com/questions/3...error-handling

I wish I had known about MZ-Tools back when I was doing Access
development full-time.

--
HTH,
Bob Barrows