Error propagation

[ajaykgarg]

Hello

I have multiple procedures A, B, C, etc.

A calls B and B calls C.

I define error handlers in all my procedures as this:-

Please Login or Register  to view this content.

Please Login or Register  to view this content.

I was hoping that if there is an error in procedure B, i will get the message "FATAL ERROR in B!"

This will help me in quick debugging of errors.

But, it seems error gets propagated to calling procedure, and I always end up getting the error message defined in first procedure: "FATAL ERROR in A!"

Is there a way for error message to be returned from the procedure where the error occured?

Thanks
Ajay

[TMS]

Not sure what you mean.

Please Login or Register  to view this content.

Gets both error messages.

We probably need a more realistic example.

Regards, TMS

[MarvinP]

Hi ajay,

How about having a single GLOBAL VARIABLE that is changed to the procedure name the first line the procedure starts. Then if there is an error you call the single error routine and it will display the current value of the error variable which is the name of the Sub being run.

See http://www.ozgrid.com/VBA/variable-scope-lifetime.htm for more on global variables.

[ajaykgarg]

This is what I am trying to do.
And you are right. In this simplistic example, it works fine.
I guess I need to look at my code again, and see what am I missing.

Thanks

Please Login or Register  to view this content.

[ajaykgarg]

Hi ajay,

How about having a single GLOBAL VARIABLE that is changed to the procedure name the first line the procedure starts. Then if there is an error you call the single error routine and it will display the current value of the error variable which is the name of the Sub being run.

See http://www.ozgrid.com/VBA/variable-scope-lifetime.htm for more on global variables.

Thanks, Marvin!
If I can't figure out why my code is not working, I will go for this solution.

Thanks
Ajay

[MarvinP]

When things aren't like you think, you are thinking something wrong!!

I think you think "Exit Sub" does exactly the same thing as "End Sub" and I'm not sure that is true. I'd have to check that assumption somehow.....

I also wonder when you do your first
On Error GoTo ErrHandler the code points to the ErrHandler that is in your Sub A. Because you don't EXIT SUB it still knows where that is and keeps waiting for an error...

How about changing the name of ErrHandler for each Sub...
Like ErrHandlerA, ErrHandlerB, ErrHandlerC and see what happens.

Overcoming each of these unknown problems makes you a better programmer.

I think the answer is hiding in this site:
http://www.cpearson.com/Excel/Scope.aspx Read it and learn.

[TMS]

Your code, as repeated here (with a slight mod: dimming z) works for me as expected.

Please Login or Register  to view this content.

AFAIK, the label (ErrHandler) is local to each subroutine. And, although subroutine A calls subroutine B, and subroutine B calls subroutine C, each subroutine only knows about its own error handler label. If I change the label in subroutine C to something else, I will get a compile error so clearly it's not happy to accept a previously defined label.

Why not share the "real" code?

Regards, TMS