Error handling VBA Code

http://www.cpearson.com/excel/errorhandling.htm

As you can see from the link I gave above, if you handle the error in one procedure then the error is no longer there when you return to previous procedures. And this is obviously the problem if you want to stop executing code in all previous procedures.

Two solutions:
1 Only have error handling in first procedure
2 If you catch an error in any procedure then you can re-trigger the error in your error handler using

Err.Raise Err.Number

This send the same error back to the previous procedure where you hopefully handle it too

Jeg prøver Err.Raise Err.Number
Tak

"Jeg har i dag en klassisk error handler så jeg kan se fejlen - men herefter ønsker jeg at total stoppe programforløbet og gå til start"

Hvad mener du med, at du kan "se fejlen..og gå til start"? Jeg er bare nysgerrig, fordi jeg har samme udfordring og har valgt at sende en boolean retur gennem hele program-hierarkiet. Det er besværligt, især når den skal mosles sammen med de øvrige argumenter, jeg vil returnere. Jeg synes, at det er pænere end at fremprovokere en fejl for at kunne 'komme tilbage med den'.

"Jeg synes, at det er pænere end at fremprovokere en fejl for at kunne 'komme tilbage med den"

"!og har valgt at sende en boolean retur gennem hele program-hierarkiet."
But you still have to check the value of the Boolean in every procedure, and it also means you cant use a bollean as a return value for other things.

Nothing at all wrong throwing the same error if that's what it takes

"Jeg har i dag en klassisk error handler så jeg kan se fejlen - men herefter ønsker jeg at total stoppe programforløbet og gå til start"

Actually there may be an easier solution, but it depends what you mean with "....og gå til start"

If there is some code you want to execute in the first procedure then I think that one of the options in  #1 is correct. But if you want to terminate execution of all code then

just add

End

in your error handling routine

EG:

On Error GoTo TheEnd
    i = 1 / 0
     
    Exit Sub

TheEnd:

MsgBox "Error …." & Err.Number
End

End Sub

Terry: "But you still have to check the value of the Boolean in every procedure, and it also means you cant use a bollean as a return value for other things."
I use my own types to pass to and from functions/procedures. In case you need to, you could have a array with an error code in first place. In my opinion, this is "nicer".

"In my opinion, this is "nicer" ;-)

You did see the solution using End in #5? Maybe you could use that yourself

I did - but I don't like END in the middle of the procedure/function code either. Well, now per2edb has some options..

"but I don't like END in the middle of the procedure/function code either" you are hard to please arent you ;-)

Næh. Det er helt almindeligt, at eksekvering af kode afsluttes i bunden af proceduren. Jeg ville f.eks. aldrig skrive:
....
If boolvar then
End..
Else
Fortsæt kode
End If

End Sub/Function
---

I stedet ville jeg sørge for, en if-then-else-endif, som så afsluttedes i bunden:
If (not boolvar) then
Fortsæt kode
'else er tom
Endif

End Sub/Function

Men programmeringsstil kan jo diskuteres i det uendelige...

"Men programmeringsstil kan jo diskuteres i det uendelige" your right there ;-)