Advertisement

07.06.2008 at 09:41PM PDT, ID: 23542465
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.2

Error Handling with Parent and Child procedures

Asked by jdana in Access Coding/Macros, Visual Basic Programming

Tags:

Two procedures, "Parent" and "Child" have error-handling code shown below.  The Parent procedure calls the Child procedure.  The Child procedure occasionally throws an error.  When it does, the compiler runs through the error-handling code in the Child procedure, then jumps back out to the Parent procedure and continues to run code in the Parent procedure.  I don't want this occur.  If an error occurs in the Child procedure, I want the compiler to jump to the ErrHandler in the Parent procedure as well.  Is there a way to configure the error-handling code in the Parent procedure to regard any error in the Child procedure as an error in the Parent procedure as well?Start Free Trial
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
Sub Parent (or Sub Child)
   ' Procedure header not shown.
   On Error GoTo ErrHandler
 
   ' Procedure body not shown.
ExitProc:
   Exit Function
   
ErrHandler:
   MsgError Err.Description, Err.Number, vbCritical, strTITLE
   Resume ExitProc
 
End Sub
[+][-]07.06.2008 at 10:25PM PDT, ID: 21942886

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Access Coding/Macros, Visual Basic Programming
Tags: VBA (Office v11)
Sign Up Now!
Solution Provided By: zorvek
Participating Experts: 1
Solution Grade: A
 
 
 
Loading Advertisement...
20080924-EE-VQP-38 / EE_QW_2_20070628