Err.Line should do the trick -- IF you have numbered the lines of your
procedure as though it were an old-time DOS basic. Few of us go to that
trouble, these days... it can be done programmatically, but I haven't had
the need, so don't have any code to offer.
I tend to do my initial debugging without error handling, with the "break on
unhandled errors" option set, so that the debugger takes me directly to the
offending line. Then, I add error handling. But, of course, that doesn't
help if you've put your app in the hands of the users and want to know where
they encountered the error!
Larry Linson
Microsoft Access MVP
"WindAndWaves" <ac****@ngaru.com> wrote in message
news:WZ*******************@news.xtra.co.nz...
Is it possible to find out at what line an error occurred for an error
log???
---
Please immediately let us know (by phone or return email) if (a) this
email contains a virus
(b) you are not the intended recipient
(c) you consider this email to be spam.
We have done our utmost to make sure that
none of the above are applicable. THANK YOU
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.687 / Virus Database: 448 - Release Date: 16/05/2004