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
We are experiencing this same behavior in Version 2207 now, and no possible Trusted Folder/File combination fixes it... I confirmed it has nothing to do with any code updates by opening a version from May that worked just fine previously that exhibited the same behavior of leaving a ghost process.
- I have just started experiencing the same in 2209 (Build 15629.20208 Click-to-run 32 bit).
At first, I thought it was my project.
However, I can create a brand new accdb file and add a form, which will then open and close without issue. As soon as I whack a button on said form and save it, I get the issue. Access removes the lock file on close, but leaves the process open. Hi,
ToddP What is your Office Build No?
Did you try to revert to the previous build? (see Daniel's description or Microsoft's)
If the problem does not occur with the previous build, that would be a strong indication of an update bug.
Servus
Karl
Access News
Access DevCon- Reverted to 15330.20230 and it's still leaving a process running in the background, but at least I can re-open the files successfully and it doesn't add a process each time the file is opened.
Then I reverted to 15330.20196 and it does the same thing.
Now I'm thinking that this has just been going on longer than I thought.
My concern with these processes running is what state is the file actually in when just killing the process. Or is there something else causing this?- Hi ToddP. You may have tried this but I would start by checking if a process is left when opening a new blank accdb. If that doesn't leave a process running, I would be looking at autoexec macros, startup functions/procedures etc. of any db that does leave a process. And of course... the debugger's cardinal rule, "What's changed?"
Karl_Donaubauer current build is 15427.20210
Karl_Donaubauer Just got the Office Deployment Tool setup to revert a 'few' versions to test that out so I'm working on that, was just really hoping someone else might be able to offer something better to avoid that for ALL affected computers.
