[AccessD] Error Code Generator

I do it the way you just mentioned.  I have a global errorhandler, that
receives the information I want to 'monitor' from each procedure.  It saves
time and space, and with a central point for errorhandling, I can force
things pretty easily.  (Record the errors in a db, shut the system down,
etc.)

Drew

-----Original Message-----
From: artful at rogers.com [mailto:artful at rogers.com] 
Sent: Friday, September 22, 2006 12:33 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Error Code Generator

I didn't write it, but it raises a question that I have wondered about for a
while. Why is it better to embed the error routine in the particular proc or
func than to write one global error handler and pass it the text and perhaps
the proc/func name, so there's only one error handler in the whole app? I
never did understand this. Can anyone provide some insight?

Arthur

----- Original Message ----
From: Martin Reid <mwp.reid at qub.ac.uk>
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Sent: Friday, September 22, 2006 1:19:04 PM
Subject: [AccessD] Error Code Generator

I believe someone on the list created an error generator. I believe it might
be JC? Anyway I have been using it a lot for code examples and just to be
politically correct want the owner to know. Example below
 
 
Function CopytoWss()
On Error GoTo Err_CopytoWss
    DoCmd.SelectObject acTable, "Contacts"
    DoCmd.RunCommand acCmdExportSharePointList
Exit_CopytoWss:
Exit Function
Err_CopytoWss:
        MsgBox Err.Description, , "Error in Function CopytoWss"
        Resume Exit_CopytoWss
    Resume 0    '.FOR TROUBLESHOOTING
End Function

 
Martin
 




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