Breakpoints Not Working

[Paul H]

Hi, I am trying to edit another old database. Overall it doesn't look like too difficult a task, one form, one report, two small modules. To understand the code, I'd like to step through the code and validate the logic, get comfortable with it and make the necessary changes, but after placing breakpoints almost everywhere, I've been unable to get the code to stop so I can step through the process. I've validated these are the correct subs by clicking on the "build" button on the form's Event boxes. The only way I can validate the code is running is by inserting a msgbox function which gives me some sort of visual clue.

Here's a pic of the form load sub.





It blows through two breakpoints, displays the msgbox, then disappears even when I respond with a Control + Break. Is there some setting in VBA that overrides this or a security setting I don't know about? Till a few hours ago this was a .mdb Access 2003 file. I just upgraded it to an accdb. I am using Access 2010.

Signed,
Dazed and confused.

[RuralGuy]

I would start by *importing* everything into a fresh new db and see if the problem follows. It only takes a minute.
http://btabdevelopment.com/how-to-im...-new-mdb-file/

[Micron]

Lost my post (must've hit F5 again). Suggestion was that the connection between form and code was broken in spite of what the builder suggests. Could also copy code, remove [Event Procedure] from form property sheet, save/close/reopen, recreate [Event Procedure] and paste in code, being careful not to have two sub/end sub lines. BTW, posted code for the form does nothing anyway - it's all commented out.

[Paul H]

" posted code for the form does nothing anyway - it's all commented out."

Intentionally. I really don't want to run any code until I can walk through it. I put the message box in there (and elsewhere) so I could establish that it was actually executing the code.

I would start by *importing* everything into a fresh new db

I'm going to try that and/or see if I can find a different copy of the mdb that works. I'll get back to you.

[Paul H]

The import to a new db worked. Thanks RG.

[RuralGuy]

You're very welcome. Any time my database starts acting weird, it is one of the first things I do. It tends to leave any corruption behind. Enjoy your project.