Dan Waters
dwaters at usinternet.com
Thu May 21 16:46:19 CDT 2009
I've been using this for several months now at three different customers. Getting started is a learning curve, but the results are worth it. For each error, you can log the entire call stack, and the values of each variable in each procedure in the call stack. I've also added additional variables in some procedures just to give me more information if an error occurs. For error logging, I set up 3 tables with a 1-many relationship between them, and appropriate reports. Also, Wayne Phillips of EverythingAccess.com spent some time explaining to me how to set this up in a system with a Main.mdb and a referenced Library.mdb. I would suggest that you give it a try if resolving errors is something you need to do. Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Robert Sent: Thursday, May 21, 2009 4:20 PM To: 'Access Developers discussion and problem solving' Subject: [AccessD] What do you guys think about this... Looks very interesting, but.... http://www.everythingaccess.com/simplyvba-global-error-handler.htm WBR Robert -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com