I have my code append to a text file if there is an error. But the
results are vague. I'm just having it append the Err.Description to
the file. Err.Source doesn't tell me much. Is there a way I can also
append the procedure name where the error occured? Even better would
be the procedure name AND line number. But.. one can dream, I suppose.

Any suggestions or related help appreciated.

tod

The procedure name is not available as far as I know, so you would have to
manage it yourself. One way would be to have a global public variable, and
set that whenever a procedure is entered.

--

HTH

Bob Phillips
... looking out across Poole Harbour to the Purbecks
(remove nothere from the email address if mailing direct)

"tod" wrote in message
m...
I have my code append to a text file if there is an error. But the
results are vague. I'm just having it append the Err.Description to
the file. Err.Source doesn't tell me much. Is there a way I can also
append the procedure name where the error occured? Even better would
be the procedure name AND line number. But.. one can dream, I suppose.

Any suggestions or related help appreciated.

tod

Look at Stephen Bullen's information on ERL

http://tinyurl.com/2fh2u

and on his central error routine. Read the entire thread.

--
Regards,
Tom Ogilvy

"tod" wrote in message
m...
I have my code append to a text file if there is an error. But the
results are vague. I'm just having it append the Err.Description to
the file. Err.Source doesn't tell me much. Is there a way I can also
append the procedure name where the error occured? Even better would
be the procedure name AND line number. But.. one can dream, I suppose.

Any suggestions or related help appreciated.

tod