Re: Error Handling
- From: "Arvin Meyer [MVP]" <arvinm@xxxxxxxxxxxx>
- Date: Thu, 13 Aug 2009 15:09:58 -0400
"Dirk Goldgar" <dg@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C6895378-7049-4E9D-824F-E451E984156D@xxxxxxxxxxxxxxxx
"Douglas J. Steele" <NOSPAM_djsteele@xxxxxxxxxxxxxxxx> wrote in message
news:%23cPoz2CHKHA.4432@xxxxxxxxxxxxxxxxxxxxxxx
In any case, I don't believe what you want to do is possible.
Until recently I didn't think it was possible, but have you seen this?
http://www.everythingaccess.com/simplyvba-global-error-handler.htm
It still requires a single line reference to it in each procedure. That's
all my code needs as well. Allen's code does the same. The difference I
think is that mine creates an external error log which it will create on
first use, and Allen's writes the log to a table within the database. I
chose to do it my way in case the database was corrupted, the user could
just email me the plain text file.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
.
- Follow-Ups:
- Re: Error Handling
- From: Wayne Phillips
- Re: Error Handling
- From: Dirk Goldgar
- Re: Error Handling
- References:
- Error Handling
- From: Shell
- Re: Error Handling
- From: Douglas J. Steele
- Re: Error Handling
- From: Shell
- Re: Error Handling
- From: Douglas J. Steele
- Re: Error Handling
- From: Dirk Goldgar
- Error Handling
- Prev by Date: Focus jumps a control
- Next by Date: Re: Error Handling
- Previous by thread: Re: Error Handling
- Next by thread: Re: Error Handling
- Index(es):
Relevant Pages
|