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.)
Our community of experts have been thoroughly vetted for their expertise and industry experience.
The Most Valuable Expert award recognizes technology experts who passionately share their knowledge with the community, demonstrate the core values of this platform, and go the extra mile in all aspects of their contributions. This award is based off of nominations by EE users and experts. Multiple MVEs may be awarded each year.
The Distinguished Expert awards are presented to the top veteran and rookie experts to earn the most points in the top 50 topics.