[AccessD] vbWatchdog error handler

[Stuart McLachlan]

Me too. :)

Error handling should be pro-active.  Untrapped errors that require this sort of framework are 
an indication of poor design and testing.
It's just a PITA that the VBA developers have never bothered to implement  Try...Catch and 
you have to resort to IFs and/or the clunky On Error Goto.

In the rare event that a user finds a new way to break the application,  they will generally let 
you know and you can implement a fix.

I can see it being useful during pre-release testing, but not in production.


On 30 May 2023 at 5:28, Gustav Brock via AccessD wrote:

> Hi Dan and John
> 
> I must say, I´ve never understood the need for extensive error
> handling. We test our applications very carefully, thus errors are
> extremely rare and certainly not happening on a daily basis.
> 
> /gustav
> 
> Fra: Daniel Waters<mailto:df.waters at outlook.com>
> Sendt: 30. maj 2023 02:48
> Til: Access Developers discussion and problem
> solving<mailto:accessd at databaseadvisors.com> Emne: Re: [AccessD]
> vbWatchdog error handler
> 
> Hi John,
> 
> I used this up until about 5 years ago.  It's an excellent addition,
> and much more than worth the money.  Set up a table to store the error
> data, create a report that shows that data, and set up a daily email
> so you'll know of any errors that occurred yesterday at each of your
> customers.  Or you can set up an immediate email for any error or if a
> certain type of error occurs.
>