John W. Colby
jwcolby at colbyconsulting.com
Sun Jan 11 21:57:06 CST 2004
Susan, The problem with that perspective is that the function that handles the error knows the context of the error, i.e. specifically what the program was doing at the time it happened. Sure, a "disk full" is a disk full regardless, but even then it may be on a zip where you want to prompt the user to change disks or something. OTOH, a "can't save the record because a field doesn't meet the criteria" is very specific to the table / field / form etc. I have a generic error handler but it is only to handle things like jet errors that occur during a query when other error handlers fail to trap the error. Things like that. John W. Colby www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Susan Harkins Sent: Sunday, January 11, 2004 9:25 PM To: AccessD at databaseadvisors.com Subject: [AccessD] error questions Any of you work with a generic error-handler for an entire module or perhaps even a public function instead of repeating possibilities in individual functions? Repeating error solutions and it seems inefficient. Susan H. _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com