Password Protect a Back-End Database

zyousafi

Registered User.
Local time
Today, 22:49
Joined
Jun 13, 2010
Messages
39
I rely heavily on Microsoft Access in my office environment and there are multiple applications that have multiple concurrent users. End-users always seem to find a way to use an application in a way other than actually specified. Attrition here is high so people keep changing and simply training them or trusting them not to do the wrong thing is not enough. I want to put passwords on my back-end databases; however how will the front-end remain linked to the back-end when I do this? I have tried doing this numerous times; however every article on the internet makes it seem as easy as stealing candy from a baby. Every time I try doing this I am successfully able to put a password on the back-end database and successfully use the Linked Table Manager to re-link the front-end to the back-end; however when I close the front-end and try reopening it I get the blank Microsoft Access screen. Please note that I am using Microsoft Access 2010.
 
Does this mean what I am trying to do cannot be done?
 
Why not put an auto exec that opens a modal form asking for a password in the backend?
 
Thank you for the response! Perhaps I have done a poor job of explaining the situation. I have a FE and a BE for my Access Application - the BE is hidden in a hidden network folder that every user essentially has to be given "Read" and "Write" access to. I have distributed the FE to all of the users which is currently 200+. In an ideal world the users should enter data using the FE; however I have a bad feeling that some of the users have located the "hidden" network folder and maybe entering data directly into the BE. I have searched on this top for quite some time and I have been told that there should be no issue in putting a password on the BE and the re-linking the FE to the BE; however whenever I do that and try opening the FE again I see a blank Microsoft Access page.
 
Hi

Access 2010 has a bug in relinking tables.

In its FE:

1) Delete all linkages and after use the Compact and Repair
2) Re-link the tables again and use the Compact and Repair.

If not resolve, create a new BD. Export all objects except the linked tables. Bind the tables in the new database and immediately use the Compact and Repair.

Success!
 

Users who are viewing this thread

Back
Top Bottom