Forum Discussion
Solved
Access doesn't close properly. A remaining background process can only be terminated in task manager
Since yesterday I noticed that in all my Access databases there is a problem when I close them. When I close a database, it leaves a background process that can only be terminated in Task Mana...
- Yes, here also the update available (Europe). Tested en fix the problem. Trusted Location not necessary any more. But I highly recommend it. Otherwise you will have problem starting from April. MS is blocking marcos. Check https://techcommunity.microsoft.com/t5/microsoft-365-blog/helping-users-stay-safe-blocking-internet-macros-by-default-in/ba-p/3071805
I have experienced the same problem. When I terminate the running process and open the database from within the Access interface then the program opens and when I close it the running process terminates. However, when I try to double click on the database file in windows explorer the database does not open. I can at that point still open the database from within Access but then when I close the database the process remains running the the record locking file remains open. If I then terminate the task manager process and again open and close the database from within Access, the record locking file closes.
- This is a slight variation on infrequent problem, but one which seems to occur consistently once it appears in a particular accdb. Unfortunately I have not found a resolution and a discussion in a group of current and former Access MVPs did not yield any definitive answers or suggestions.
George_Hepworth The only and final solution is a button and docmd.quit acsaveall.
- I'm glad to hear that works in that situation. Unfortunately, it is not generalizable.
