Disabled Breakpoint continues to stop code

[Glenn_Suggs]

Hello everyone... I had to put a breakpoint into my VBA code in one of my apps to debug a problem I was having and inspect the variable values. All was well until I finished the debugging process and tried to eliminate my breakpoints. However, the next time I ran the application, the code stopped as if one of the breakpoints was still active. I closed the application and reopened it (even rebooted the computer) and the code continues to stop in the same spot in the program. I'm wondering if anyone else has ever seen this happen and what I should do about it? The only thing I can think of to do is to create a new empty Access database and import all the obects from the old one. I'm thinking the database must be corrupt and this is all I know to try. It's kind of a large database and that could take some time. Any ideas? Thanks in advance... Glenn

[SteveH2508]

Make a small change to your VBA code (e.g. add then remove a space or something).

Compile your code. That should fix it.

If not, then google 'de-compile access'.

[ranman256]

Yes. I still get this too. And since I cant compile (other errors that are irrelevant) , it comes and goes.

[ssanfu]

And since I cant compile (other errors that are irrelevant)

Errors are not "irrelevant"!! The errors need to be fixed, then compile and repair. You are flirting with disaster.
If the really are "irrelevant" (ie test code), comment out the code block. Then Compile and Repair.

Also, you are probably editing the code while it is executing (single step mode) ....NOT a good thing to do.
I know - I almost lost my database because the VBA project corrupted.