I have a form that pops up, when you press the close button it runs some code
that does some general cleanup. The code is working fine, but even though
there is no breakpoint sent in the debugger, when I click this button the
debugger pops up and appears with the yellow arrow pointing to the first line
of this exit handling routine.

It does not show a break point on this line, but the Microssoft Visual Basic
title bare indicates [break]

If I continue it runs fine. If I cause this form to pop up again it exits
without breaking. Also if I reload the database using the file menu and go
to this form I can exit without the debugger poping up, but if I exit access
and go then load this database, then exiting from this popup will once again
cause the debugger to appear in break mode as if a breakpoint had been hit.

What is causing this problem and how do I stop it from happening.

"eredleaf" <(E-Mail Removed)> wrote in message
news:120D294A-D062-4C53-AC97-(E-Mail Removed)
> I have a form that pops up, when you press the close button it runs
> some code that does some general cleanup. The code is working fine,
> but even though there is no breakpoint sent in the debugger, when I
> click this button the debugger pops up and appears with the yellow
> arrow pointing to the first line of this exit handling routine.
>
> It does not show a break point on this line, but the Microssoft
> Visual Basic title bare indicates [break]
>
> If I continue it runs fine. If I cause this form to pop up again it
> exits without breaking. Also if I reload the database using the file
> menu and go to this form I can exit without the debugger poping up,
> but if I exit access and go then load this database, then exiting
> from this popup will once again cause the debugger to appear in break
> mode as if a breakpoint had been hit.
>
> What is causing this problem and how do I stop it from happening.

Sometimes "ghost" breakpoints are left behind in code as a result of the
development process, especially if you edit code while the form is
running. Try opening the form in design view, opening the form's code
module, make a minor change to any line of code (such as changing a
letter and then changing it back), and then click Debug -> Compile.
Save and close the form. Now try it out and see if that has fixed it.

If it hasn't, you might try adapting these instructions, posted by "'69
Camaro", aka Gunny, on 13 January 2005:

--------- begin quoted post ---------
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.
--------- end quoted post ---------


--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)