VBA debugger does not stop at breakpoints

[Chris Zoumas]

Hi, I have an mdb file of Access 2000 with lots of tables, forms, classes
and a size of about 12MB.
Suddenly before two days the VBA debugger stopes to respond to any
breakpoint (skips the breaks)
that I insert in the code editor. Could anyone provide me with some hint.
The problem
appears only for the specific mdb file (even in another machine).

TIA, Chris

 

[Allen Browne]

Hi Chris

The symptoms you describe indicate a corruption.

1. Make a backup copy without overwriting any previous backups.

2. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect.
Explanation:
http://members.iinet.net.au/~allenbrowne/bug-03.html

3. Compact the database to get rid of any temp stuff, including the Name
AutoCorrect junk.

4. Decompile the database by entering something like this at the command
prompt while Access is not running. It is all one line, and include the
quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

5. Compact again.

6. Compile.

You should find that it is working again now. If not, rebuild the database
by following the 6 steps for Symptom 1 in:
Recovering from Corruption
at:
http://members.iinet.net.au/~allenbrowne/ser-47.html

To prevent the corruption recurring, you may want to stop editing in break
mode. This one is actually speculation, but the reason is #5 in:
Preventing Corruption
at:
http://members.iinet.net.au/~allenbrowne/ser-25.html

 

[Dirk Goldgar]

Hi, I have an mdb file of Access 2000 with lots of tables, forms,
classes and a size of about 12MB.
Suddenly before two days the VBA debugger stopes to respond to any
breakpoint (skips the breaks)
that I insert in the code editor. Could anyone provide me with some
hint. The problem
appears only for the specific mdb file (even in another machine).

In addition to the possibility of corruption that Allen Browne
mentioned, it could just be that the option "Use Access Special Keys"
has been turned off in the Tools > Startup options dialog. If that
option is checked, breakpoints will be ignored. I'd check that first,
before addressing the corruption issue.