Access 2013 Trust Center Macro Settings

I have a small .accdb file that resides on a server.The file is used as part of version control process. It is automatically opened by more that 100 users on 100 work stations every time a new version of an application is available. The problem is that I seem to have to open the file once for every user on every work station to set the Trust Center Macro Settings to Enable all macros. So I have set that setting every time we have a new user on some work station.

Is there not some what to set that once and have it apply to all users on all work stations?
rmkAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
Not really. TL's need to be set in each person's Registry.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
Somewhere on Gunter's site (http://www.ribboncreator2013.de/en/) ... he has code to automate this at least ...instead of manually having to do it.  I used his code to create an EXE that I can email to users (here at work) that will set the TLs and Macro Security setting.  I use it frequently.,

mx
0
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

rmkAuthor Commented:
Could I ask the network administrator have a .reg file run at each user login with the following contents?

[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Access\Security]
"VBAWarnings"=dword:00000001

[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Access\Security\Trusted Locations]
"AllowNetworkLocations"=dword:00000001
0
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
You could ... but I suspect good luck with that.  But hey ...

mx
0
rmkAuthor Commented:
I'm confused as to how all of this works. The registry tree for the VBAWarnigs entry implies that it should be a global setting for the user. Yet it "seems" that some users have a problem opening \\server\setup\setupmgr.accdb but have no problem opening a file further down \\server\setup\15.0\setup.accdb. Is that possible?

I spoke with the network administrator and he already been setting the AllowNetworkLocations entry in a login script. So he's going to add the VBAWarnings to the login script and we'll see if that helps or not.
0
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
The registry settings must be on the workstation, not the server (although the server may need reg changes as well, depending on where that file is located).

I could see where a folder that was "downtree" from another could allow access, but and "uptree" folder would not (or the other way around, for that matter). Just because have permissions on C:\Folder1\Folder1A\Folder1AA does not mean I have permission on C:\Folder1\Folder1A.
0
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
"although the server may need reg changes as well, depending on where that file is located"
Fortunately, I never had to do that here at work.

Trusted Locations need to include the Folder (and any subfolder) on the Server where that back end is location, as well as where the FE resides on a local workstation.
And be sure to check "Subfolders of this location are also trusted" ... And "Allow Trusted Locations on my network."
0
rmkAuthor Commented:
I just met with the network administrator again and got some different information this time.

The login script for VBAWarnings did not set the registry entry. So he looked further into the AllowNetworkLocations setting and found that he was not using a login script to set it. He was setting it via group policy which probably explains why the AllowNetworkLocations check box is checked (but disabled) in the Access Trust Center Settings. He has used group policy to EnableAllMacros. We'll have to what a while to have it propagate to the servers and network. I'll test it later this evening or early tomorrow morning by re-booting my work station and let you know if that solves the problem or not.

BTW, all the appropriate users do have read / write permissions to all the appropriate server folders. I probably just don't accurately recall exactly what worked and didn't work.
0
rmkAuthor Commented:
It looks like group policy worked. After rebooting a work station the EnableAllMacros radio button is selected (and disabled) in the Access Trust Center settings and everything seems to be working fine.
0
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
Cool.  You have officially circumvented Macro (in)Security :-)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.