My code ignores breakpoints at runtime

[Peter Beckett]

Does anyone know why I have the following problem? I'm
completely stuck with developing my project any further
until I can find the solution. It's probably something
completely simple & obvious.

To test my code, I insert some breakpoints. I turn to
the form which invokes the code, but it doesn't stop at
the breakpoints, whether in the class object or the
module.

1. This doesn't happen if I return to some of the
earlier versions of the same project; there, the
breakpoints work as expected.
2. I know the relevant code is running, because the
Debug.Print lines are effective on each pass, & if I put
a new MsgBox line in after the break, the dialog box
comes up when I run the code.
3. Putting a Stop statement or a complile-able but
illogical line in the code doesn't seem to help either,
but maybe I haven't thought of anything quite illogical
enough!
Does anyone have any ideas?

 

[Dan]

I wish I had an answer for you, I posted the same
question over a month ago, received no reply. I have
talked to seasoned VB & VBA developers & showed them on
my machine, they have no explanation.

Only suggestion was to use a MSDN help request to
Microsoft, I do not have a license to do this.

If you get a fix on this, I would greatly appreciate an
email on what you found.

Regards,

Dan

 

[John Spencer (MVP)]

I've had similar things happen, but I've always been able to fix them by

-- Making sure all Tools: Options Name Autocorrect options were not checked
-- Selecting Debug: Clear All Breakpoints in the VBA window
-- Compiling

If that didn't clear it up then additional step
-- Compacting the database
-- Decompiling the database
-- Save and compact

No guarantees, just what has worked for me in similar situation.

 

[david epsom dot com dot au]

Tools, Startup, Advanced: "Use Access Special Keys"

If it's not that, use the /decompile command line option
to reset the project.

(david)