Forum Discussion
Access doesn't close properly. A remaining background process can only be terminated in task manager
- 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
Hi KiwiMarkNZ, Thanks for letting us know about the solution you found. Unfortunately I am not a Grammarly user and have never installed it. However, reading the thread, I was reminded that disabling EoAExperiences.exe solved the problem for me. I plan to try that again.
Nononono, this should not at all be an issue. One says this, one says that. The fact remains:
If you have an Access Database with certain code in it, certainly some ActiveX components, which are MS supported, logically the Database should close properly, when clicking the close button.
This is not happening, and it is not Microsoft's doing, it is impossible to anticipate all behaviours or all possible outcomes when a user (the person that made the database first of all), has not determined his or her, cause of the problem.
I know that somewhere, over the years, I added so much code, references, non-updated or, - not anymore compatible of properly closing - objects, controls, data, etcetera...
So I know I have to close MS Access, MS doesn't. So If make a button, with the docmd.quit SaveAll and the work is done.
Remove the cross to close the database, so there is no discussion possible of how to close my db.
