Guus2005
AWF VIP
- Local time
- Today, 19:37
- Joined
- Jun 26, 2007
- Messages
- 2,641
Just dropping it here: FYI:
I didn't know it and never used it but the End statement is a real showstopper.
When the End statement is encountered all code execution stops, waiting for the next event. Even in nested for end loops.
So when you have a callstack, you won't after this command: End
You can use it when you don't want the error code to bubble up?
Can't think of a good purpose for this command. The example code is not a good example of what it does.
Share & Enjoy!
I didn't know it and never used it but the End statement is a real showstopper.
Code:
Public Sub trythis() As Boolean
On Error GoTo trythis_Error
Debug.Print 1 / 0
On Error GoTo 0
Exit Function
trythis_Error:
End
MsgBox "Error " & Err.Number & " (" & Err.Description & ") in procedure trythis of Function Game_Control"
Resume Next
End Function
So when you have a callstack, you won't after this command: End
You can use it when you don't want the error code to bubble up?
Can't think of a good purpose for this command. The example code is not a good example of what it does.
Share & Enjoy!