The second option for handling errors at runtime is to Break in Class Modules
when there is no error handling present. This option is used for projects that contain class
modules, especially projects that are using ActiveX components created as other Visual Basic
projects.
When debugging ActiveX components, it will be important for you to see the code
that generates an error in the ActiveX project. With this option you need to be able to see
the line of code that generated an error in a class module. If you did not use this option,
errors generated in a class module would return back to the client program instead of breaking
in the class module.
Breaking in class modules is different than breaking on all errors when error
handling is in place. If Break in Class Modules is selected and error handling
is in place for the code that generated a runtime error, the error handler would
be executed and the continued program execution would depend on that error handler.
