"breakpoint" off yet compiled program stops

[Martyh]

Is there a way to eliminate the problem of stopping a program from going to the code side of the module and stopping (as if it were in the debugging mode) in the middle of a perfectly good program that has been compiled? THe places where it stops are places where a last set a breakpoint, and compiled the code without the "breakpoint". In other words, I clicked the "breakpoint" off and then compiled the code.

Thanks,

Marty

 

[RuralGuy]

I believe a /decompile will get rid of those "phantom" break points.

 

[Martyh]

Thanks RuralGuy !

Does this work in access 2003 as well? --- I don't see any mention of that!

Marty

 

[Banana]

While /decompile will fix this definitely, a simpler fix sometime is to go to that line where the phantom breakpoint is, copy the line, then delete the line, insert a new line then paste the same code back in.

Yes, /decompile should work in most of version, including 2003.

 

[jonno_g]

While /decompile will fix this definitely, a simpler fix sometime is to go to that line where the phantom breakpoint is, copy the line, then delete the line, insert a new line then paste the same code back in.

Thank you so much for this solution!

That problem has been bugging me for years!!!

 

[Banana]

Glad to see you were able to find the archive and solve your problem.