[AccessD] Error Code Generator

Think of it like this:  If you don't at least trap the error in the
procedure where it occurs, how do you expect to get that information?
Errors that are unhandled in a procedure bounce back up until they find
an error handler.  By that time, you have no idea where they originated,
you only know what the error is.  So even if you have a "global" error
handler, you still need to trap errors in the procedure so you know
where to look for the problem.

Charlotte Foust 

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

That was precisely my point. It seems the logical way to do it, but all
the generators and the built-in stuff likes the local version. I don't
get why that would be better. Given modern chip speed, it's obviously
not about jumps. Maybe all the code does compress nicely but the local
way seems so clumsy to me.

----- Original Message ----
From: DWUTKA at marlow.com
To: accessd at databaseadvisors.com
Sent: Friday, September 22, 2006 1:51:07 PM
Subject: Re: [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
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




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