Question : App Stops at breakpoint after they have been removed

I routinely user temporary breakpoints when testing new code or code that isn't behaving properly.  For clarifiaction: I do this by clicking in the margin next to an executable line of code.  Access puts a brown dot there and when execution hits that line of code, executions stops and the line of code is highlighted in yellow.  Pressing the right arrow in the command bar lets execution continue.
These breakpoints are all removed by Access when the app is closed or I can remove them by selecting the 'Clear breakpoints' option from the 'Debug' dropdown.  When I remove them the app behaves correctly (no more stops at clear breakpoints), at least for me.

Whenever my changes are complete and tested I put the app in production for the users.  I always compact and repair and compile the app before putting the MDB (not MDE) in production.

Lately the users have been complaining about the apps stopping for no apparent reason.  When I inverstigate I see that the app is behaving just as if my breakpoint was still there.  It stops on the exact line of code where I had my temporary breakpoint, with the line highlighted in yellow.  There is no brown dot next to the line of code.  I have educated the users to just press the left arrow key to have the app continue but they (and I) are pretty annoyed by this behaviour.  I can usually remove the 'residual breakpoint' by de-compiling then recompiling the app.  However, I have been using Access for over ten years and have never encountered this behavoiur before.  It is only on this clients network that the issue occurs.

Has anyone else encountered this or can anyone explain it?  It only happens on one clients network.

Answer : App Stops at breakpoint after they have been removed

....never encountered this behavoiur before....

You've just been lucky then.  I think most developers here have seen it and the solutions are along the lines  you have indicated. Personally I cut the module code out and then past it back in again when I see the problem.