We experienced this problem. Our main Access 2000 switchboard launches other Access 2000 instances. We noticed that after our last application (Access 2000 switchboad) closed, that MSACCESS was still a running thread, and was consuming most of the CPU.
We made a simple change to the code...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.