Can you give me a better idea of what you mean by catching errors? That could mean a lot of things.

Michael Hi Michael, I mean that I need my software not to exit the program on an error condition, but have a higher level "catch" of that condition which handles it gracefully. I'm writing a musical score editor for personal use in my spare hobby time. Because it's just a bit of spare time, I can't make a promise my software won't have bugs. When I'm working on a score, I don't want to lose my work when an error occurs, such as internal errors that violate the invariants I've established in my data structures. So any action that results in an error should

Michael Snoyman wrote: trigger a message box that says "such-and-such error" and otherwise leave the data unchanged. Then I can save my work and attempt to debug the problem. Thanks, Mike