Find a way to prevent "phantom breakpoints" in the VBA IDE, this has been an issue for 20 years
We all know about these; an end user runs your Access application, and it freezes up and suddenly displays the VBA code window to the user with a line highlighted in yellow. The user is confused and concerned, and thinks it's a bug in the program. A quick random edit and recompile usually fixes this, but how about fixing the problem that these breakpoints really do get cleared when you click to Clear All Breakpoints? In some business environments you can't only deploy MDE or ACCDE files.
Andy Rice commented
I second this. Something MS should fix.
Mark Burns commented
You can fix this yourself by following documented Best Practices.
1) Open the database using the /Decompile command line switch.
2) Compress & repair the database
3) re-open & re-compile the code manually
4) Compress & repair the database
Voila! All phantom breakpoint stops are gone!