The Trust Centre that doesn't trust me or my PC (1 Viewer)

[Cotswold]

I have recently started with security and Trust Centre problems. Up until then I have never had the need to even look at Trust Centre, never mind use it. I now
have all folders used by Access set to Trusted and with subfolders ticked. The copy of Access in use is 2019 and it is set not to be updated. An example is: a database with only tables when opened Access, a right click does not allow Design to open on a table but if the table is opened with shift then design is available.

I am wondering if anyone has any recent issues with the Trust Centre, which to my mind I find pretty pointless anyway.

What that I totally fail to understand, is that Access knows there is a cause for an error but does not share what it is. Basically some bright spark at MS
having written the code to locate what they imagine to be errors, has deliberately withheld providing the slightest chance of ever locating and fixing it. What is the point in that?.

This is one of the typically unhelpful messages from Access. If you click on a Learn More, you do not learn more.

 

[The_Doc_Man]

This is one of the typically unhelpful messages from Access. If you click on a Learn More, you do not learn more.

Yep, proof positive that it is a Microsoft product. If using SHIFT works, I guess it objected when you were being shiftless.

OK, to be serious for moment...

Perhaps there is some kind of automation running on startup, either a macro or an opening form with an active class module. Could either kind of startup automation be going on in your case? Because the SHIFT key bypasses opening automation. For you to get tweaked in a way dependent on the SHIFT key, that's the first place I would look.

If you can execute code after startup, the question is, what did you do to enable that? I would almost be tempted to run the code in a non-trusted location to see if the shift key gets you past the opening, then try to use some other automation and see what error it gives you, if any.

 

[Cotswold]

Thanks for that Doc. But I'm not running the database, I'm just opening it to alter, amend and update forms etc.
If I open it in its original folder, no probs. Transferred to my current folder up comes the error. I don't have any macros In the database. It makes no sense and hours wasted punching clouds. If I import all of the contents of the old 2022 database into a new empty database no errors at all. All I can do is pointlessly create new databases and import the contents of the old to fix the 'Trust' error and hope all will be well going forward.

The only slight difference is that the contents of the database and its related BE were imported and updated from an Access 2000 .mdb version to Access 2010 .accdb. That was then first opened and modified in Access 2019 on a different PC. The software was then transferred the this PC and updated, amended and run in my year 2022 folder set without issue. It was the year 2022 database that then fell over when shifted to my 2026 folder set.

I do wonder if MS has updated my version of AC2019 against my wishes because I have had no problems until recently. Maybe some residue from AC2000 resided in the database that the new and supadupa Trust Centre doesn't like?

 

[sonic8]

This is a weird problem I haven't heard about yet.
As your DB works in one folder without those security warnings but not in the other, I would strongly recommend to double and triple check the Trusted Locations in Trust Center.

 

[Cotswold]

Thanks Sonic but it seemed that I spent most of yesterday afternoon doing that.
I have added the folders with this issue into Trusted Locations. All with the main Folders individually set as trusted and in desperation I also added the paths to its subfolders. Even with a separate line in trusted locations for each subfolder. All to no avail. From a note on one folder it would appear that I first noticed this issue on the 10/9/25 and must have worked around it then. Thinking about it, that was probably the first date when I used the Trust Centre. Software cannot decide to do something differently from one day to the next. So against my specific request MS must have updated my version of Accss2019 around September 2019.

There is no doubt that creating a new database FE & BE in the new folder, then importing all of the objects into it from the older ones with errors solves the issue. If I remove the folder set from the trusted locations, when I reopen the FE I get the message "Some active content has been disabled" and the button [Enable Content] " As normal, that fixes the mysterious active content. When I restore the folder into the Trust Centre, it opens normally. I have now created new tables and imported the objects into them from the old tables. The problem hasn't been solved, I've just found a way around it. At the end of the day, you can't let MS defeat you!

 

[The_Doc_Man]

Thanks for that Doc. But I'm not running the database, I'm just opening it to alter, amend and update forms etc.

If you run the DB by double-clicking the file's icon, you are implicitly running the DB. If it has a default startup action, it will perform it, even if the next action is merely to display a navigation pane. Using the SHIFT-key bypasses startup operations. In my book, that is strong evidence that something "startup-ish" is going on. Whether you know it or not, you DO have some kind of startup. Whether an AutoExec macro or a Startup Form, I don't know with certainty (though I think you would have seen a visual effect for an Opening Form.)

 

[Cotswold]

There is definitely no macro. Only the autoexec which I always have renamed on the FE as Autoexec1 to prevent it working during development. Neither do I have the display form set. I have never used macros in access except for Autoexec because when I started out with Access they just seemed more trouble than they were worth. However, after this I will be removing the Autoexec from my programs as I update them and switch to VBA for opening.

But I had similar issues with BE data which had only table objects. I still wonder if it was due to the fact that it was originally a conversion from Access2000 that the Trust Centre doesn't like.
I'll see if I can attach an example to this post in a short while.

** EDITED** Unfortunately I've replaced them all. I created new databases and imported all of the objects from all those with the problem. Then I pasted all of the new over the old. If I happen to come across the problem again I'll post one.

 

[Isaac]

Microsoft has basically, by nuance and implication, relegated VBA development to the "we really don't recommend you use this" category.
It's sad, for such a useful tool!

 

[Cotswold]

It does appear that you aren't far out there Isaac.