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
Not all of our apps were leaving tasks behind. If quit was NOT in the same function called via Autoexec then the would be an orphan task. An hourly scheduled task which was problematic stopped producing orphans when its quit was moved into the top level function. (Access 365)
- I think it may be time to have another pair of eyes on your application and trace the program flow to isolate the problem(s). This does not appear to be an Access problem per se but rather a coding issue.
- It is not my application but an ancient legacy one that started leaving orphaned tasks. My only change was to delete one quit command in a sub-function which was already covered in the initial autoexe function and not needed.
- In that case, perhaps an excellent testing scenario would be to restore that quit command to see if it might address your problem with a process left running.....
