Dan Waters
dwaters at usinternet.com
Fri Sep 22 12:54:35 CDT 2006
Hi Arthur,
I've done that for years, and it's been really helpful in knowing when a
customer is having a problem. The system emails me the list of errors
everyday so I can see if anything new has cropped up.
Dan Waters
-----Original Message-----
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 ----
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