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
Problem solved for me:
In/with Microsoft Access open I went to
{File{Options{Trust Center -> then{Trust Center Settings} then {Trusted Locations} then{Add new location
I then browsed to the path were my database was, then clicked {ok} to add to the list.
This seemed to solve the Problem I was having.
Does this mean I can no longer use databases in any other folders? If I say the C:\ folder is ok, does doing so include all sub folders?
In/with Microsoft Access open I went to
{File{Options{Trust Center -> then{Trust Center Settings} then {Trusted Locations} then{Add new location
I then browsed to the path were my database was, then clicked {ok} to add to the list.
This seemed to solve the Problem I was having.
Does this mean I can no longer use databases in any other folders? If I say the C:\ folder is ok, does doing so include all sub folders?
Andrew2265 That's actually an interesting question in a different way. I would ask it this way, should one EVER place accdb/accdes in untrusted locations? I think not. That's the reason for the Trusted Locations approach in the first place.
That said, it's up to your organization to determine its security plan.
No, you have to explicitly tell Office to trust subfolders.
- Thanks for your Response, some data is not “Trusted Data Location” worthy. Tanks sizes, Pump sizes, water flow calculation data, etc. If there is hundreds of projects, each in their own folder, and each project has it’s own Access Data file, or other Microsoft Files, It seems problematic to declare each folder “Trust Worthy” I guess one could organize all projects under a main “Project Folder” and then do the subfolder declaration.
I guess in some organizations where un-trustworthy people might be working or have access, then perhaps “Trusted Data Locations” is critical. But in some cases, it seems unnecessary.- A proliferation of accdb files is something that I hadn't considered, to be sure. If I had to do that, my impulse definitely would be to create that Project Folder and ensure that all such accdb files are stored there under the Trusted Folder designation. The alternatives is to place them randomly around the network, which I doubt is the case anyway.
