In the code window, choose Options on the Tools menu.
On the General tab, make sure Error Trapping is set to:
Break on Unhandled Errors
While you are there, make sure Compile On Demand is unchecked, as that can
corrupt the database.
If you are still stuck, you may be able to temporarily work around it by
adding the line:
Stop
instead of a breakpoint.

Signature
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
>I have a database (FE + BE) in A2000 which has suffered some
> corruption (I think). The problem is that the Break Point facility no
[quoted text clipped - 35 lines]
>
> Peter Hibbs.
Peter Hibbs - 18 Jan 2008 14:47 GMT
Allen
The Break on Unhandled Errors option makes no difference and the
Compile On Demand option has always been unchecked.
I entered the Stop command in the code but this made no difference,
i.e. the code just executed as if it was not there.
Any other ideas.
Thanks.
Peter.
>In the code window, choose Options on the Tools menu.
>On the General tab, make sure Error Trapping is set to:
[quoted text clipped - 7 lines]
> Stop
>instead of a breakpoint.
Tom Wickerath - 18 Jan 2008 20:55 GMT
Hi Peter,
In order for a break point to be honored, you must have the option "Use
Access Special Keys" enabled. This option is found under Tools | Startup. A
restart of Access is required if you find that this option was not enabled.
I'm not sure about the other issues you've mentioned, such as the Stop
statement not being honored, and the error trapping not working.
Tom Wickerath
Microsoft Access MVP
https://mvp.support.microsoft.com/profile/Tom
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________
> Allen
>
[quoted text clipped - 9 lines]
>
> Peter.
Peter Hibbs - 18 Jan 2008 21:56 GMT
Hi Tom.
Yes, that fixed the Break Point problem. I can't think how that flag
got disabled but it was and break points now work.
Regarding the error trapping, I now think that is a different issue. I
am doing some more testing on another PC and am making some progress.
If I get stuck I will start another thread.
Thanks again for the help, yet another thing I will have to remember
to check.
Peter.
>Hi Peter,
>
[quoted text clipped - 24 lines]
>>
>> Peter.