Long error handling section, safe to break out?

Hello;

Following the basic error handling on this page
http://support.microsoft.com/kb/168336, many of my functions therefore have
quite long error handling sections, compared to their actual function of opening
a database connection and perhaps calling a stored procedure.

How 'safe' is it to put some of the ADODB error handling into another function?
If I am already inside an error, should I really be calling other functions?

Follow - does it make a difference to the function that there is a final "GoTo
Done", instead of a "Resume Done" ? Is there any effective difference between
the two?

Many thanks
sdg

.

Relevant Pages

  • Re: Run cmd button in code
    ... Calling the event ... directly leaves you unsure of how to handle errors that might occur. ... event you need to trap the error, for a function you can allow the error to ... and you needed to change the error handling you could never rely on an ...
    (microsoft.public.vb.general.discussion)
  • Re: [Patch] mm/sparse.c: Check the return value of sparse_index_alloc().
    ... we must deal with the failure condition when calling it. ... This lock keeps two different sections from ... reallocating for the same index ... Do you want to try to add some actual error handling to ...
    (Linux-Kernel)
  • Re: Run cmd button in code
    ... > You have my complete support simply calling cmdTwo_Click! ... See my post re error handling. ... Michael ... Prev by Date: ...
    (microsoft.public.vb.general.discussion)
  • RE: Error Handling on using Common Dialog...
    ... Regardless of any issues with the common dialog, ... handling in every single procedure. ... basic error handling. ... the guys here on this group but it doesn't have error handling for the ...
    (microsoft.public.access.modulesdaovba)
Loading