Application opens up in Debug mode

[Geoff]

Has anyone seen this? We have an Access 2003 application that seems to have
a "phantom breakpoint." Open a particular form and you find yourself in
Debug mode (with the yellow arrow on the left margin indicating what line is
executing next). Click "continue" and the application proceeds as it should.
Close that form, open it again, this time it does not stop at the "phantom
breakpoint." Close the application completely, open it again, and the same
thing happens as before.

Any idea why this is happening?

Much obliged.

 

[Fred Boer]

Hi Geoff:

Here's a quote from a past post that might help:

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.

HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

 

[Jeff Conrad]

in message:

Has anyone seen this? We have an Access 2003 application that seems to have
a "phantom breakpoint." Open a particular form and you find yourself in
Debug mode (with the yellow arrow on the left margin indicating what line is
executing next). Click "continue" and the application proceeds as it should.
Close that form, open it again, this time it does not stop at the "phantom
breakpoint." Close the application completely, open it again, and the same
thing happens as before.

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.

HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
Good luck,

 

[Jeff Conrad]

in message:

Hi Geoff:

Here's a quote from a past post that might help:

Great minds think alike Fred.
;-)

 

[Geoff]

Thanks guys. I gotta wonder how anyone ever figured out that fix. Click 3
times!?!? at least we didn't have to say "There's no place like home..."

 

[Jeff Conrad]

in message:

Thanks guys. I gotta wonder how anyone ever figured out that fix. Click 3
times!?!? at least we didn't have to say "There's no place like home..."

You're welcome (on Gunny's behalf).

 

[Geoff]

It seemed to work at first but the problem is still there.

 

[Geoff]

The fix originally suggested worked at first, but the problem soon
re-appeared for no apparent reason. This time we commented out the code with
the phantom breakpoint, compacted the database, uncommented, and so far it
seems fine.

 

[Jeff Conrad]

in message:

The fix originally suggested worked at first, but the problem soon
re-appeared for no apparent reason. This time we commented out the code with
the phantom breakpoint, compacted the database, uncommented, and so far it
seems fine.

Hi Geoff,

Glad things *seem* to be Ok now. You still might consider doing a decompile
on this database (make a good backup first) and import everything into a new
container to clear out any remaining dust bunnies.