Debug Error Messages Are Supressed

W

wrldruler

I have a novice developer at work, and he asked for help on a
particular database.

When an error occurs in his database, on any of his forms, the debug
error message does not pop-up. The form just stops processing. I have
to use Msgbox statements to figure out where the code is stopping. A
pain.

I can't find any "Resume Next" statements, or any error handling. And
it's strange that this seems to happen on all his forms.

I can't figure out how he accidently disabled all Debug messages in
his database.

Any ideas?
 
A

Allen Browne

1. Open the Immediate Window (Ctrl+G) and enter:
DoCmd.SetWarnings True

2. Open the code window, and choose Options on the Tools menu.
On the General tab, set Error Trapping to:
Break on Unhandled Errors.

If it still fails after this, you need to to decompile.
Follow (at least) the first 6 steps on this page:
http://allenbrowne.com/recover.html
 
W

wrldruler

FYI. This issue has been fixed.

The database had never been compiled, so I am sure that was the
problem. However, I refused to compile it because he had so many
little errors, it would have taken me hours to clean up his mess.
Amateurs.

Instead, I simply opened up a blank database, imported a couple of his
main forms, fixed all the errors, compiled, and then imported his
remaining objects. Did the trick -- error messages are back.

Thanks
 
A

Allen Browne

Thanks for posting the answer.

What you did makes sense for fixing the particular issue. All the best for
the longer-term maintenance issues though. :)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top