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
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?
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?"
- I've now discovered I have been chasing two issues, and I thought they were just connected and one was causing the other. I have still not solved my mystery for why a process is staying open in the background, but that at least appears to be a more isolated issue. The other issue was that the programs were crashing on other computers immediately when opening, but appears to be resolved now by late binding a subform that was recently added.
