Break point persists after all breakpoints have been cleared

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

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 o
On the second & subsequent encounters with the line of code no break is implemente
The line is not flagged as a break point
 
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 said:
In Access 2k3 I added a break point to chase an error. The error has been
Click to expand...
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.
 
Thanks Ke

----- Ken Snell wrote: ----

VBA sometimes "remembers" a breakpoint even after being cleared. What I d
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 int
memory)
3) Compile the database (if the code line is integral to the cod
syntax, replace the line of code after deleting it with something else fo
the moment)
4) Insert the deleted line of code at the appropriate place by usin
Ctrl + V
5) Compile the database again

This usually takes care of the phantom breakpoint for me

--
Ken Snel
<MS ACCESS MVP

Terry said:
In Access 2k3 I added a break point to chase an error. The error has bee
Click to expand...
fixed and the break point cleared. However, Access insists on breaking o
the same line BUT only the first time Access encounters the line of code. I
I press the F5 key the code continues to run and works flawlessly until th
database is opened in a new instance of Access
 
Back
Top