Re: Break point persists after all breakpoints have been cleared

From: Ken Snell (kthissnellis9_at_notcomcast.realnet)
Date: 04/11/04


Date: Sat, 10 Apr 2004 20:19:23 -0400

VBA sometimes "remembers" a breakpoint even after being cleared. What I do
in these cases is this:
    1) Highlight the entire line of code on which the break is occurring.
    2) Press Ctrl + X to remove the line of code (and to copy it into
memory).
    3) Compile the database (if the code line is integral to the code
syntax, replace the line of code after deleting it with something else for
the moment).
    4) Insert the deleted line of code at the appropriate place by using
Ctrl + V.
    5) Compile the database again.

This usually takes care of the phantom breakpoint for me.

-- 
       Ken Snell
<MS  ACCESS MVP>
"Terry" <anonymous@discussions.microsoft.com> wrote in message
news:0948A477-6D6F-4BAD-83E9-BF9321671E7F@microsoft.com...
> In Access 2k3 I added a break point to chase an error. The error has been
fixed and the break point cleared. However, Access insists on breaking on
the same line BUT only the first time Access encounters the line of code. If
I press the F5 key the code continues to run and works flawlessly until the
database is opened in a new instance of Access.
> I have cleared all break points, the code compiles ok
> On the second & subsequent encounters with the line of code no break is
implemented
> The line is not flagged as a break point


Relevant Pages

  • Re: Code breaks despite error handler
    ... > Comment out the line on which the breakpoint occurs. ... > can compile without it. ... Close the database. ... That's what causes the ghost breakpoints. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Access xp - Why does debugger break in when I have no breakpoi
    ... And thanks for not pointing out my basic math miscalc: the original post was ... today with an Access database somebody else wrote. ... Comment out the line on which the breakpoint occurs. ... can compile without it. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Code breaks despite error handler
    ... >> Comment out the line on which the breakpoint occurs. ... >> can compile without it. ... Close the database. ... That's what causes the ghost breakpoints. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Code breaks despite error handler
    ... Access xp - Why does debugger break in when I have no ... Comment out the line on which the breakpoint occurs. ... can compile without it. ... Close the database. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Me.ControlName = Something
    ... Steve, I think you will discover that my original diagnosis was probably correct, and that whatever is actually triggering the Form_BeforeUpdate event's firing is actually where the problem lies, not the Form_BeforeUpdate even itself. ... Compact the database to get rid of this junk: ... Still in the code window, choose Compile from the Debug menu. ... > Private Sub Form_BeforeUpdate ...
    (microsoft.public.access.formscoding)