"ghost" break

[Guest]

I have a recurring problem with a database I'm working on. I have all
breakpoints cleared and saved. However, occassionally, the code will stop as
though a break was there; usually where the most recent break was located.
Now, if I am working on the DB and have this happen, I do a "clear all
breakpoints" and "compile" - then save, and it seems to clear out.
Sometimes, I do a compact and repair, just to be sure. Then, things are
fine. However, last week users started having this problem... and I haven't
had to go into code on the active copy for quite some time! When I do the
above steps I mentioned, it works for me, but it continues breaking for them
(even if they have exited and rentered the program).

Any ideas on what might be causing the "ghost breaks"???

THANKS!

 

[Fred Boer]

Dear TRM:

Here is a past post by on this issue which might help. The author is
"Gunny", as per links below post:


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.

 

[Guest]

Thank you! I'll follow the instructions... glad to know what causes it!