Trusting my own ACCDB

[Dick Watson]

What's the minimum way to trust the code in my own ACCDB file short of just
turning the whole thing off for everything? I'm getting tired of clicking
the security warning stuff, but self-signing does not seem to be an option
since it seems to only apply to packaging it and, once unpackaged, doesn't
appear to care anymore.

Curiously, the Help for Digitally Sign a Code Project doesn't: It says one
option for Word, Excel, or PowerPoint, another option for Visio, Outlook or
Publisher, and nada about Access.

 

[Allen Browne]

Include the folder where your ACCDB file resides, as a trusted location:
Office Button | Access Options | Trust Center | Trust Center Settings

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

message
news:[email protected]...

 

[Dick Watson]

Is that the narrowest way? That implicitly trusts anything else in that
folder, not just my db. You'd think there was a way to make Just One db file
trusted.

 

[Allen Browne]

Put it in its own folder?

What I personally do is to trust all the databases in my Data folder. If one
arrives from a questionable source, it goes into a temporary folder, not
where my own databases reside.

Since I have over 700 databases on my hdd, the idea of trying trust each one
individually is not appealing to me. Neither is digital signing: some of
these belong to clients I support who modify their own databases. Trying to
keep track of all those certificates and keep the certificates up to date
for every modification of every database is worse than a joke, not to
mention the problems when converting versions.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

message

 

[Dick Watson]

I surely agree that the "trusted locations" model has its place. It's not
what I'd prefer to do, but it surely has its place.