Add a trusted location with Access 2007 Runtime (1 Viewer)

DataMiner · Oct 2, 2007

How in the world do I add a trusted location with only the Runtime version of Access 2007 installed on the PC?

I am in the process of distributing some new runtime-only applications; how do I stop the irritating "potential security risk" warning from coming up everytime the user logs in??? I can't figure out how to get to the "trust center" with only Access Runtime installed. Users don't have any other 2007 applications like Word or Excel either, and are running Windows XP, NOT Vista.

Zigzag · Oct 2, 2007

Hi Dataminer,

When you package your application up for deployment there is a stage where you can add a digital signature. When the application is then opened on the clients PC (As long as the macro security level has not been set to high) then the client has the opportunity to install your signature. The next time your application is opened there is a check box that can be clicked to always trust this signature. After this has been checked you will not see the message again.

So in brief, search forum for Digital Signature

Garry

Zigzag · Oct 2, 2007

Me again,

Just reread your post, what I have posted is aimed towards Access 2003. Maybe someone will will put me right if it doesnt apply to 2007.
Sorry for any misleading info.

Garry

DataMiner · Oct 3, 2007

I am not doing anything like "packaging my application for deployment". My applications are all used internal to my company, and I just
1. Install Access runtime
2. Copy the FE onto the PC.

This has worked fine for me for many years... up until Access 2007, with it's additional security "features". It still works OK... just an ongoing irritation to have that "potential security risk" thing pop up every time. Especially when the only help document microsoft has says to go use a menu that's NOT EVEN THERE when you're using runtime.

boblarson · Oct 3, 2007

This should help you:

http://www.thescripts.com/forum/post2752405-4.html

DataMiner · Oct 4, 2007

Access 2007 runtime, still getting security warning

Thanks, that certainly looks like it would help, but after manually editing the registry I'm still getting the security warning. (at least I didn't seem to break anything).

My "trusted location" is on a network drive, not a local drive, so I think I have to also find a way of editing the registry that is the same thing as clicking the "Allow network locations" box in the Trust Center.

After reviewing the Registry settings on the one PC where I have the full version of Access installed, it looks as if there is a Registry setting:
[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\TrustedLocations]
AllowNetworkLocations(REG_DWORD) = 1

So I added this manually to the PC where I have only Access Runtime installed. Again, didn't seem to break anything, but I'm still getting the security warning everytime I start the Access application. Tried rebooting, no help.

ANy other ideas?

boblarson · Oct 4, 2007

DataMiner said:
Thanks, that certainly looks like it would help, but after manually editing the registry I'm still getting the security warning. (at least I didn't seem to break anything).

My "trusted location" is on a network drive, not a local drive, so I think I have to also find a way of editing the registry that is the same thing as clicking the "Allow network locations" box in the Trust Center.

After reviewing the Registry settings on the one PC where I have the full version of Access installed, it looks as if there is a Registry setting:
[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\TrustedLocations]
AllowNetworkLocations(REG_DWORD) = 1

So I added this manually to the PC where I have only Access Runtime installed. Again, didn't seem to break anything, but I'm still getting the security warning everytime I start the Access application. Tried rebooting, no help.

ANy other ideas?

Sorry, no I don't.

dsfcom · Apr 16, 2008

I too am looking for a solution to a similar problem. I have tried manually adding trusted locations, changing allownetworklocations to "1", changing allowuserlocations to "1", and nothing is working. If anyone knows the appropriate registry changes to make please post.

mdecaney · Apr 29, 2008

after digging though the registry, i have found the way to manaully add a folder to trusted security and i have found this to work with both local and network paths.

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\Trusted Locations\Name_For_Path_Goes_Here]
"Path"="PATH_To_Database"

the easiest way we found to distrobute this is by having the registry file silently imported at user login.

AC5FF · Apr 30, 2008

I just worked this issue yesterday.
I had to check the "trust network locations" as well as add the folder as a trusted location. But after I had done this I no longer get the security warning.
I put together an instruction email to all of my users and no one is getting this warning any more. No registry hacks were needed.

jepoysaipan · May 19, 2008

Hi AC5FF,

Care enough to share your solution to this problem?

Thanks in advance!

AC5FF · May 19, 2008

Jepoysaipan

It's pretty much as I said. Off the new office button at the top left of Access I choose the button at the bottom; (Access Options). The window that opens has a selection for Trust Center. I added the network path to the trusted locations (including subfolders) and at the bottom there is another checkbox (Allow Trusted Locations on my Network) and I had to check that box as well.

Sorry I can't get more descriptive with this right now... I'm at home and still have Office2003 here. 2007 is at work

I did get my copy of 2007 in the mail Saturday, but I need serious hardware upgrades before I even THINK of attempting to install it here at home

I will try to edit this tomorrow if I can remember

craigachan · May 22, 2008

I've followed your post on this subject as I have been having problems with this too. My question to you, AC5FF, is that will all these "Trusts" follow the packaged version in runtime? You can no longer set these in runtime.

My experience has been that it works when the full version is trusted but it has not been following the packaged database on a runtime workstation which can no longer be adjusted.

So were you able to get rid of the warnings on those running runtime?

StraitJacket · Sep 2, 2008

When you add the network location you have to type it in as a UNC path. It will take it then. for example \\servername\sys\directory1\directory2\program location\

jepoysaipan · Sep 24, 2008

Hi SrtraitJacket,

Welcome to the forum!

Well, the solution that I was expecting is that after the deployment, because after you deploy the DB using the 2K7 runtime it's impossible to open and set trusted locations, now the next question is why do we need to modify trusted locations? Answer: Let say they upgraded their server, change folder name, move the DB to another server location etc. etc.

It will be very nice for the application to have this such utility much like the same in 2K3 simply call a routine (relink()...) to get the DB up and running during a scenario.

Thanks.

Jeff

stwalker · Apr 14, 2009

The following solution worked for me:

Edit registry:

Under HKCU\Software\Microsoft\Office\12.0\Access\Security
create a new DWORD key named VBAWarnings with value 0x00000001

No need to add a trusted location, the warning message does not appears anymore.

I hope this can solve your problem.

jepoysaipan said:
Hi SrtraitJacket,

Welcome to the forum!

Well, the solution that I was expecting is that after the deployment, because after you deploy the DB using the 2K7 runtime it's impossible to open and set trusted locations, now the next question is why do we need to modify trusted locations? Answer: Let say they upgraded their server, change folder name, move the DB to another server location etc. etc.

It will be very nice for the application to have this such utility much like the same in 2K3 simply call a routine (relink()...) to get the DB up and running during a scenario.

Thanks.

Jeff

craigachan · Apr 14, 2009

Works Great! Thanks a million.

AC5FF · Apr 20, 2009

I must be doing something wrong. I followed this; went to the registry as shown, and added the setting, but I still get the problems.. Hmm

craigachan · Apr 21, 2009

It worked on all my workstation except 1. I haven't yet figured out what the difference is yet.

Mike375 · Apr 21, 2009

I have not read all the thread so may have missed something

I got this from member KenHigg, copy/pasted from posting. It worked for me on Vista and XP and obviously worked for Ken. My testing was using Runtime 2007 to open DBs in A2003.

"Basicly you create a new key in the registry and tell where the trusted folder is.

a. Run the registry editor by doing Start->Run and typing in regedit
b. Navigate to the following folder:

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\A ccess\Security\Trusted Locations\

c. Highlight the 'Trusted Locations' folder, right click and do New->Key
d. You can name this whatever you like.
e. Then highlight the new key and right click and do New->String Value
f. Name the new String Value 'Path' (without the quotes)
g. Highlight the new 'Path' key entry, right click and do Modify
h. Here type in the path to your new trusted folder something like:

c:\mynewfolder\

Ok to save, close the registry editor and it should work."

Add a trusted location with Access 2007 Runtime (1 Viewer)

Registered User.

Registered User.

Registered User.

Registered User.

Smeghead

Registered User.

Smeghead

Registered User.

New member

Registered User.

Registered User.

Registered User.

Registered User.

New member

Registered User.

New member

Registered User.

Registered User.

Registered User.

Registered User.

Similar threads

Users who are viewing this thread