Trusted Location

KenHigg

Registered User
Local time
Today, 16:58
Joined
Jun 9, 2004
Messages
13,291
Been a while since I tinkered with this - Can you set up a trusted location for a 2003 database? If so, where / how do you set up the key in the registry?
 
Been a while since I tinkered with this - Can you set up a trusted location for a 2003 database? If so, where / how do you set up the key in the registry?

2003 doesn't use Trusted locations Ken. That started with 2007. In 2003 there are some security warnings that do occur unless you set the macro security to low or use the registry settings. (I can't seem to find any page with them listed, but I'll keep looking)
 
Thanks for the input. I must have played with them in a 2007 db I did a couple years ago. I guess we'll be happy with the self-signed certs.... :)
 
Hi Bob et al,

OK. So, I created a working accdb(Access 2007) database. Then I turned it into an accdr and put it on the network. My users copy a version onto their desktop for testing. However, when they run it prompts them to enable macros.

Is there a way for me to set the accdr to run without the user having to say it's OK to open the accdr because of the user's security settings for Access2007?

Also, I noticed when they are running on their desktop there were UNEXPECTED error messages and flags that did NOT appear when I'm running on MY DESKTOP?! Is it due to security settings? Because it runs perfect and supersmooth on my desktop.

thanks!
 
Also, everything runs SUPERSLOW on the FE(frontend) version for the other users. It's superfast for me. But it's the EXACT same version I put on the network drive and then copied it to the deskstop for each users(including me). Not only that, some of the UI disappeared when they run it on their desktop and it's perfect on my version. How can this be?

hmm..
 
1. Yes, they can get errors if they do not have a trusted location set up. If they are using the Runtime (not full version of Access) then they would need to set up the trusted location like this shown here:
http://accessjunkie.com/faq_33.aspx

2. There will be no Ribbons for users who use the Runtime or an accdr with the full version of Access. You need to provide your own Ribbons in that situation.

As for slowdowns you might have to work through the Access Performance FAQ located here:
http://www.granite.ab.ca/access/performanceldblocking.htm
 
1. Yes, they can get errors if they do not have a trusted location set up. If they are using the Runtime (not full version of Access) then they would need to set up the trusted location like this shown here:
http://accessjunkie.com/faq_33.aspx

2. There will be no Ribbons for users who use the Runtime or an accdr with the full version of Access. You need to provide your own Ribbons in that situation.

As for slowdowns you might have to work through the Access Performance FAQ located here:
http://www.granite.ab.ca/access/performanceldblocking.htm

Bob,

1) Do they put the trusted location as where the FE sits(on their desktop) or the BE location on the network drive?
(Note: If it's the BE location then I can set that in the accdb version then when I convert it over to accdr version that network drive BE location will be considered safe. If it's the FE location, then how would I know where they put their FE? It could be their desktop? Some subfolder location or just about anywhere?)

2) I don't need to provide Ribbons for that since I have switchboards with buttons to navigate through.

3) I'll need to read up on that to speed up the FE/BE interactions with multiple users. For just me, it seems instant!

thanks!

flyinghippo99
 
Last edited:
The frontend needs to be in a trusted location as that is the part that needs to have macros and vba enabled.
 
The frontend needs to be in a trusted location as that is the part that needs to have macros and vba enabled.

Figured that much in the interim. So, it seems I have to manually set it on each user's desktop as part of the installation....
 

Users who are viewing this thread

Back
Top Bottom