Phantom break points - how to avoid?

[btidwell3]

To All,

From time to time, I have problems with what I call, "phantom" break points. After making changes to the VBA code in an Access application that I support, users will call saying that the app has broken out of an action and is displaying the VBA editor with a line of code highlighted. This always throws the users into a panic.

Does anyone know how to avoid this? The only fix I know of is to delete the line and retype it. But this is irritating and always causes a reissue of the application.

Does anyone know how to avoid this stupid phenomena?

Later,
Bill T.

 

[PaulBricker]

I have seen this when I am testing some code. When I am satisfied that the code is running the way I want, I go to the menu bar and go to Debug...Clear All Break Points. Then I save the module and make one final run thru of the code to make sure there are no breakpoints happening. That's about all I can think of.

Paul

 

[jadams0173]

I've had uses tell me the same thing. The way I fixed it was to delete the line and save the code and close the mdb file. The reopen and insert in the line of code back in.

May be overkill but it worked.

I tried to have patience but it took to long! -DW

 

[btidwell3]

jadams0173,

That is what I am doing now, but this is a pain in the caboose. It triggers additional support calls. I causes me to find the code problematic code line and replace it. Then issue a new version of the application.

I wish that MS would deal with this.

Before issuing a new version, I clear all breakpoints (Debug menu) and recompile and still these things occur occasionally.

Thanks for the input.

Bill T.

 

[CautionMP]

btidwell3,
Have you tried to Decompile your project? It will fix most of the mystery problems with Access modules.

Hope this helps,
CMP

[small]For the best results do what I'm thinking, not what I'm saying.[/small]
(GMT-07:00) Mountain Time (US & Canada)