[AccessD] Error Trapping

A long time ago I co-wrote and then Seth Galitzer ported to VB a wizard for
inserting an error handler into one specific function, in every function in
a specific module or in every function in every module.  You can press a
button to just insert error handlers everywhere that no handler already
exists.  I highly recommend doing that.  I use this myself pretty much daily
as I am writing code, and on occasion when it appears that I have let a
function slip through that is causing issues.

It is available as a download from our web site - 

http://www.databaseadvisors.com/downloads.htm

Click VBErrorHandler to download it.  View the readme and install it.  You
will then have a toolbar in the code editor for inserting the error
handlers.  It can also be used in Word and Excel BTW.

John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Wednesday, August 02, 2006 11:14 AM
To: AccessD
Subject: [AccessD] Error Trapping

For a long time I've seen that an error trapped in one procedure may have
actually occurred in a called procedure.  For example, if Procedure A calls
procedure B and an error occurs in B, then the error might get trapped in A,
not in B.  So my error log shows an error trapped in A, but I need to know
that it happened in B.

Is there a way to accurately know which procedure actually triggered an
error?

Thanks!
Dan Waters

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com