Yes, experimenting I now see what you mean. The part of the story I wasn't clear on was the code after the break will execute even if the case is false which is exactly why the SC end (1) exited the script in a false case in my first post.
I was initially thinking, when the case ended in the break, the next case was immediately started, but no, not until it finished executing code after the break. I'm not sure if that a good thing or bad thing, but as you said, it can be used to our advantage. Thanks.
Edit: Help states,
Usually each case should be closed by a break statement. Else processing continues with the next case (sometimes though this can be desired).
That makes sense and Don provides a good example. It certainly seems inconsistent though that when a case is false, code after the break within that case is executed before the next case is looked examined. Whereas, if the case is true, the code after the break is not executed. I would think Don might want to clarify that in the help file if that's what he intended.