Link to home
Start Free TrialLog in
Avatar of mlunsford
mlunsford

asked on

Microsoft Access Security Notice

I'm developing a run-time based Access 2007 application for a client.  I need to be able to set it so that the users do not get security notices every time they start the application.  I initially thought I was running into Trusted Location issues (see this question; however, I added code to create a trusted location and that did not stop all of the security notices.  My client is still getting the "Microsoft Access Security Notice" every time they start the application, even after verifying that the trusted location for the app had been set.

I found the KB stating that users can fix this by installing Office 2007 SP2; however, my client is running Office 2010

What specifically is causing this and how can I get rid of it?  
Avatar of Exl04
Exl04

ASKER CERTIFIED SOLUTION
Avatar of Sheils
Sheils
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of mlunsford

ASKER

Exl04,

I tried changing the SandBoxMode and that did not eliminate the error (even after setting it all the way down to 0).
SOLUTION
Avatar of Boyd (HiTechCoach) Trimmell, Microsoft Access MVP 2010-2015
Boyd (HiTechCoach) Trimmell, Microsoft Access MVP 2010-2015
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Yes, I have the database split into a data BE and a logic FE, with the FE compiled into an ACCDE.  The entire Access portion of the database is distributed to each user (it does connect to some remote databases, but those are entirely outside Access and the requests are passed through a web service).

I think I may have found a solution here: http://bytes.com/topic/access/answers/764640-disable-access-security-notice

I'm waiting to hear back from the client to see if that removed the notice on their end.
I just heard back from the client and changing "VBAWarnings" did not help.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
"it may not be you project/access" with this I mean that the problem may not reside in you project
Exl04,

Thanks for your advice.  The application will be distributed to end users in a non-controlled environment and needs to "just work", so unfortunately, my ability to address issues is limited to what can be accomplished within the installer and the application itself.

However, after trying the "VBAWarnings" tip with my client and being told it didn't work, I realized that even though I developed the application in Access 2007 he had a full version of Office 2010 installed on his computer.  After changing the path from "Office\12.0" to "Office\14.0", it worked!  So I guess I'll need to set keys for multiple versions of Office.
“and the requests are passed through a web service” ....this will probably need to be post it in a section with IIS Sever experts too
Glad you found a solution...
One of the nice things about Access 2010 is that user only has to trust the document once.



SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Agreed and thanks for the input.  
I realized that the issue on my client's machine that was preventing Trusted Locations from being the solution, was that I was setting an Office 2007 TL and he is running Office 2010.  I set it to add TLs for both, and the issue was resolved so I can fortunately avoid using the VBAWarnings setting entirely.
RE: " I initially thought I was running into Trusted Location issues (see this question; however, I added code to create a trusted location "

I would like to see that code

thx.mx
I added a key in HKCU\Software\Microsoft\Office\12.0\Access\Security\Trusted Locations for the install location of the database.  And also one in Office\14.0.  Since the exact install location can change based on machine or Windows version, I also check the value in VBA and change it to the application folder if it doesn't match.