Breakpoints cleared but execution stops

[Eje]

I am responsible for a multiuser application in which we
add new funcionality a few times per year. I clear all
breakpoints before I compile, save and distribute the new
version. Now and then a breakpoint doesn't clear in the
new version. The execution stops without any error and
you have to press F5 to continue execution. I can't get
rid of this unwanted break. (Stop point is always one
where I have used breakpoint during the last
development.) The problem seems to "self-heal" after some
time. I have had this problem for a long time. Changing
computer for development or reinstalling Office doesn't
help. I have Office 2000 and use computers with as well
Windows 2000 as XP. Does anyone recognize this problem
and have a solution?

Eje

 

[Ken Snell]

I've noted this problem off and on. What I do to clear it in a module is
this:
-- Copy the line of code on which the phantom breakpoint "exists", and
write it into NotePad for retrieval. If the line is crucial to proper VBA
syntax (e.g., "If ... Then") and its absence would cause compiler error,
then copy enough lines to allow the deletion of those lines and still be
able to compile.
-- Delete the line(s) of code.
-- Compile the database.
-- Copy the deleted lines of code back into the module at the proper
location.
-- Compile the database.

 

[Eje]

Thanks Ken,

I will test your suggestion as soon as I can close down
the application.

Eje