Forum Discussion
Access doesn't close properly. A remaining background process can only be terminated in task manager
- Feb 08, 2022Yes, 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
This same error started for me today too, after a MS Office update applied to my laptop. Microsoft have updated something, and screwed up part of MS Access...
I see from the replies about listing the DB as Trusted Location, but mine already is. I'll see what other possible solutions look palatable. [Edit: Nope, Trust Centre had forgotten my DB location (which hasn't changed for many years). After re-adding the dir into Trust Centre, the error "Error 3048 - Cannot open any more databases" went away.
I also wan't getting the error message that pops up when active content tries to run in a non-trusted dir and it's not clear at all how the error message matches the solution, so, perhaps the MS update has messed something else up behind the scenes to do with the Trust Centre, rather than directly to do with MS Access.
- Vexen_CFeb 05, 2022Copper Contributor
Well, yesterday I posted to say that my DB was already in Trusted Location. This is because otherwise I get the "Active Content" warning and parts of it don't run. But then I realized that Windows had 'forgotten' the directory's entry in Trust Centre, and I re-added it. That fixed the "Cannot open any more databases" error.
Well today, the error returned, and Windows had AGAIN forgotten the Trusted Location, and I had to add the DB's dir into Trust Centre again.
I take it that this is all part of the errors resulting from the same MS Office update from the 2nd/3rd of Feb, and it'll all go back to normal.
- George_HepworthFeb 04, 2022Silver ContributorThanks for that information. As far as I know at this point MS has not yet completely isolated the problem, so this could prove useful experience.