security warning

harri

New member
Local time
Today, 18:26
Joined
Jul 9, 2014
Messages
2
Hello all,

I have installed an access data base on the company server, to be accessed by various networked pc that have access runtime 2010 installed.
I have short cuts on each pc's desktop that link to the data base, but when opening the DB a 'Microsoft access security notice' opens stating the source cannot be verified as trustworthy. Any ideas on how I can disable this?
I know if using the full version you can make the source ‘trusted’, but is there a way round in the runtime version?
Please feel free to shout if this is a windows issue rather than an access issue, and thanks in advance for any help/guidance you can give :)
 
Before anything else, is this database split? Backend on Server and everyone has their own front end installed on their local?
 
hello Gina, thanks for the reply.

yes, the .accdb file is on the server. various networked pc's with operating systems from XP-SP3 to windows 8.1 need to access the DB. a couple have access 2010, but most will be using access runtime 2010.
on the pc's with the full version of access I have removed the message by 'enabling all macros' in the trust centre, but don't have that option in runtime.
 
Is it split? (Not really sure if you are saying the whole file is on the Server or just the Backend.)
 
I dont think you can stop the message in run time. Users just have to ok the warning.

I suppose there must be a registry setting in there somewhere.
 
Actually, you can stop the message with a .REG file but will only work if database is split because it works locally not on the Server.
 
Hey Gina, I am having a similar problem. I don't want my users to think there is a problem with the Database security by leaving the message visible and requiring them to click ok.

I want the Security message to be removed and I would like to know how write a .REG file. Could you give me an example? Can this be done in VBA code? I'm not certain how to begin.

Thanks!
 
@andigirlsc

In meeting since AM, if no one gets here before me I'll post a .REG file later.
 
Re: [Solution] Security Warning Issues

Ok, here is how I solved my problem with the Security Warnings issue using the Access 2010 version.

Make the database a trusted file

  1. Make a backup of your database
  2. Go to Start|Microsoft Office|Microsoft Office 2010 Tools|Digital Certificate for VBA Projects (to create a digitally signed certificate)
  3. In the dialog box, give the certificate a name
  4. Open your database
  5. Apply User-Level Security if so desired (I set mine up to activate upon opening a specific form so as not to lock myself out instantaneously)
  6. Click File|Save & Publish|Package and Sign
  7. Select your certificate
  8. Choose a location to Save and give the new file a name
    (it will be saved as a package, not a database, and will show a different icon)
  9. Open the now Digitally Signed Package and click Trust all from Publisher
  10. The database file will automatically be extracted and will require you to save it to a location and give it a name. This final file will be the database that you distribute to your users.
Important:
If you follow all 10 steps and then decide to create an ACCDE file (to distribute as a Front End to your users) you will find that your ACCDE file will not recognize the certificate that was trusted when the database was digitally signed. I have not found a work around for this as of yet.

Security
Here is a User-Level Security Template I have found that works. It can be tweaked for your specific needs. It's awesome!
http://www.accessforums.net/sample-databases/built-user-level-security-w-user-management-20745.html

Here is some code to use for locking down all menus and shortcuts in Access (except the File menu). In my experience, setting all of your forms to Modal = Yes seems to help as well so that users can't click away from the open window to use the File menu. It also helps to add a password to your VBA code. The modules below all work, but require two logins under the same user name and privileges to effectively see all of the changes. A work around for that issue is to split the database, and make a copy of your Front End for yourself and a totally locked down copy for distribution to your users. As always, backup, backup, backup. Enjoy!
http://www.iaccessworld.com/how-to-disable-properties/
 
Last edited:

Users who are viewing this thread

Back
Top Bottom