What can cause Access to just stop as though it hit a breakpoint, even
though the line has not been toggled as such?
Thanks, Jim
Sounds like the debugger settings were saved when a break point was previously
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 the next time you are stepping through code, don't make any changes to the
code. That's what causes the phantom breakpoints.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
- - -
When you see correct answers to your question posted in Microsoft's Online
Community, please sign in to the Community and mark these posts, so that all
may benefit by filtering on "Answered questions" and quickly finding the
right answers to similar questions. Remember that the best answers are often
given to those who have a history of rewarding the contributors who have
taken the time to answer questions correctly.
Heh heh ... reminds me of "click your heels three times ..... in Wizard
of Oz". Must be the same type of magic :-).
I'll give this a try, thanks Gunny! Jim