Debugger not stopping at breakpoint

[debaird]

Using Access2007, I have been working on a db. The debugger was
working normally, but now I can't get it to stop at breakpoints.

I can't get any breakpoints to cause a pause in execution.

I have compiled, decompiled, and created new then imported, in
attempts to get it to behave correctly.

Any ideas why the the debugger/breakpoint quit functioning?

 

[Allen Browne]

In the code window, choose Options on the Tools menu.

On the General tab, choose
Break on Unhandled errors.

 

[debaird]

Thanks for the response Allen,

Break on Unhandled errors is checked
Compile on Demand is unchecked.

No change in behavior. I ran the diagnostics utility. It did not
correct the problem. It was working fine, but not now.

Don
ps. I love your Access web site and find it very useful.

 

[Allen Browne]

Presumably you've rebooted, and tried a different database (e.g. northwind.)

And you have verified that the code is in fact running (e.g. with
debug.print statements on both sides of the error-generating line.)

Remove any VBA add-ins you have.

If you're still stuck, it might be worth a reinstall of Office 2007.

 

[Jim Burke in Novi]

This may sound like a dumb question, but are you absolutely certain that the
statement(s) you have breakpoints on are being executed? If you know that for
a fact, ignore this. Otherwise put a message box just before and after where
you have the breakpoint to be certain. Have you tried to do a compact and/or
a decompile? If not, I'd try those and see what happens.

 

[Jim Burke in Novi]

WHoops, missed that part about decompiling, but you didn't mention a
compact/repair. If you haven't tried that, give it a shot.

 

[debaird]

Breakpoints work correctly on other Access files on the PC.

I have created a new file and imported everything in. Still no
breakpoints. Also won't honor a Stop command.

I have been working on this file for several months doing lots of
debugging.

 

[Tony Toews [MVP]]

Breakpoints work correctly on other Access files on the PC.

I have created a new file and imported everything in. Still no
breakpoints. Also won't honor a Stop command.

I've been using stop for years as I have found breakpoints to be flaky
in the past.

I have been working on this file for several months doing lots of
debugging.

Forgive me for stating this but I'm wondering if the code is even
executing. To double check throw in a few msgbox commands in a few
relevant places.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[debaird]

I've done that. The code is executing. It doesn't matter where I put
the breakpoints. They won't work, but they work fine on other files.

Don

 

[Allen Browne]

Next stage would be to copy the code out of the module.


Paste into Notepad, and save as a text file.

Delete the module from the database. (If it's the module of a form/report,
set its HasData property to No. Othewise delete it from the Modules tab in
the Database Windows/Navigation Pane.)

Compact the database.

Then create a new module (or fire up the module of the form/report), and
paste the code back in.

 

[debaird]

Thanks for your patience.

Since the behavior exists in all objects, I will need to to that for
all forms/reports/modules. I have tried the "SaveAsText" then
"LoadFromText" functions. I will try your suggestion.

Don

 

[debaird]

Well, call me a knucklehead and send me on my way. The "Use Special
Access Keys" checkbox in the Current Database options had gotten
unchecked. I Checked it and now all is right. Sorry for my
knuckleheadedness.

Thanks
Don