Several times now I've seen modules run until they hit an error and instead
of going into break mode and allowing me to debug the errors the code just
stops running. This is a problem because it seems that the entire module ran
and is then finished, however it only partially ran. Any ideas as to why
this happens or what I can do to stop it?

Thanks

Adam Bush

Some errors in VBA cannot be fixed in debug mode, so the program does not
give you the option to fix it. And yea, I also find this annoying.

The simpler solution might be if some type of error handler has been
written, such as on error resume next, goto, etc.

My suggestion would be to go through the code manually, using step-by-step,
or step-to if you have an idea where the problem is.
--
Best Regards,

Luke M
*Remember to click "yes" if this post helped you!*


" wrote:

Several times now I've seen modules run until they hit an error and instead
of going into break mode and allowing me to debug the errors the code just
stops running. This is a problem because it seems that the entire module ran
and is then finished, however it only partially ran. Any ideas as to why
this happens or what I can do to stop it?

Thanks

Adam Bush