[AccessD] Application Error logging

I've been doing this in my ISFE application (helpdesk/IT Tool app).  I
also have an 'error cleared' field.  I then have a form that I can view
all the 'uncleared' error messages to help debug them.  Some errors are
just random stuff (complex operations interrupted by the user), but
every once in a while I'll find a bug for an odd situation that I can
fix and send out an update for.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Tuesday, December 30, 2008 10:44 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Application Error logging

As everyone knows I use a framework to control my 
applications.  Part of that framework is an error logger.

MZTools has a very slick widget that can create a custom 
error logger as well as place a module name in the top of 
any module.  It can only do this one module / procedure at a 
time but it does work, and works well.

So I use MZTools to create an error handler that calls a 
custom error function which logs all errors into an error 
table.  The parameters stored are:

1) The error number and message
2) The module, function and line number within the function 
that caused the error.
3) The workstation name
4) The user ID from my Security system
5) The date / time of the error
6) An "extra info" field so I can pass my own error data
7) The FE version so I can log the version of the application

As you can see, once you retrofit an application to always 
call the error handler, this logging will tell you any error 
that occurs anywhere in your application.  It can also log 
errors silently (not pop up an error message) for processes 
that are just automation and should not use message boxes to 
display errors (which would hang the process).

I started doing this only a couple of years ago and it has 
proven immensely valuable to discovering errors that the 
users just click through and never report, errors in my 
automation code (data import / exports etc).

I am pretty much to the point where I see every error now.

If there is interest I will provide the code I use to do 
this logging.  If anyone else does this kind of logging, 
feel free to speak up and discuss what you do.

-- 
John W. Colby
www.ColbyConsulting.com
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI Business Sensitive material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.