VBA Untrapped Error Handling 2007/2010 Differences

[paulv45]

When my VBA program encounters an untrapped error, for example divide by 0, Visio 2007 reports the error and apparently resets the project.
In Visio 2010 the program fails silently and does not seem to reset the project.
If I use On Error code to trap the error, both 2007 and 2010 behave as expected.
If I screw up and don't properly handle errors, I at least want the user to know.
Does anyone else recognize this?
Thanks.
Paul