Debugger Break persists

[Laurel]

Every now and then a stop or break point in the debugger stays active, even
though I delete it. That is, I double click the red dot so it goes away,
but when I run the application it still stops at that point. This persists
even if I close the Access completely and re-enter. Sometimes I can't get
rid of it at all, and have to get a backup copy of the application. I work
on the application (same application) on several different computers, with
releases from 2000 to 2003, and different patch levels. I have no control
over this (school environment). Is it something that has been definitively
fixed in some release? Even so, does someone know how to get rid of the
persisting break point?

TIA
LAS

 

[jahoobob via AccessMonster.com]

You should have to only single click the dot. If you double click it you are
turning it off then back on.

 

[Laurel]

OK, I was misremembering the debugger keystroke. The important point is
that the dot is GONE (not yelling, underlining), but the program still stops
at that point.

 

[Guest]

This is usually caused by saving the module while a breakpoint is set. Be
sure you Clear All Breakpoints before saving the module.
--
Dave Hargis, Microsoft Access MVP

OK, I was misremembering the debugger keystroke. The important point is
that the dot is GONE (not yelling, underlining), but the program still stops
at that point.

 

[Guest]

Laurel,

My experience with this is that when this happens, first make sure all
breakpoints have been removed, then make enough of a change in your code to
again enable the "Compile" option is again available from the Debug menu.
Compile your code and that shoudl clear the issue.
--
HTH

Mr B
email if needed to:
draccess at askdoctoraccess dot com

This is usually caused by saving the module while a breakpoint is set. Be
sure you Clear All Breakpoints before saving the module.

 

[Fred Boer]

Dear Laurel:

Here is a past post by "Gunny" on this issue:

Sounds like the debugger settings were saved the last time a break point was
set at that line of code. You can open and close the database repeatedly,
and the problem remains.

To fix it, open the database, then open the form in Form View. Press
<ALT><F11> to open the VB Editor. Click the "Reset" button on the toolbar
three times. (Answer to question I know you are going to ask: Because
sometimes twice just isn't enough.) Select the Debug menu -> Compile
<DatabaseName>, just in case the code wasn't already compiled.


Press <ALT><Q> to return to Access. Select the Tools menu -> Database
Utilities -> Compact and Repair Database to compact the database. When
finished, close the database. Open the database again and open the form in
Form View, then enter text into the field that has recently been causing the
problem. The problem should be gone because you've removed the ghost
breakpoint.


And next time you are stepping through code, don't make any changes to the
code. That's what causes the ghost breakpoints.


HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

OK, I was misremembering the debugger keystroke. The important point is
that the dot is GONE (not yelling, underlining), but the program still
stops at that point.

 

[Laurel]

Thanks to all of you for the several approaches. I seem now to be able to
get myself out of this fix.