Why does Access break on cancelled break points?

Sometimes MS Access begins to pause the process (break) on a break point that had been  once set and later cancelled. It now happened on the client workstation after deployment of a big application.
What's the best way to prevent or at least get rid of this kind of errors? (Please answer only if you understand what I am talking about. Do not "Try this or that...", because it was already tried. I am asking about the best way from an expert who had suffered this. Also do not reply if you need OS / Access / Computer versions / brand for your answer, because it does not depend on them.)