Which thread? Which suggestions?
(david)
Thread-Topic: Access xp - Why does debugger break in when I have no
breakpoint .
Suggestions:
Ken Snell:
VBE sometimes remembers "phantom" breakpoints.
Two ways that I use to fix this problem.
(1) Comment out the line on which the breakpoint occurs. If the code
won't
compile without that line, then comment out a block of code so that
the code
can compile without it. Compile the code. Close the database. Open the
database. Uncomment out the code. Compile the code.
(2) Use the undocumented decompile switch when opening the database so
that
all compiled code is uncompiled.
"PathToAccessExecutable\msaccess.exe" /decompile
"PathToYourDataBaseFile\DatabaseFileName.mdb"
Jeff Conrad:
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.
