If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > PC based Database Applications > Microsoft Access > Securing my Back End database, Access 2003

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 02-08-12, 12:44
graeme706 graeme706 is offline
Registered User
 
Join Date: Mar 2010
Posts: 11
Securing my Back End database, Access 2003

Hi,

I'm using Access 2003, and have a straight forward FE and BE database. I have been trying to secure te system from prying eyes. I have put a password on the FE which is great. But anyone can open the BE and read / copy all the data in the tables.

I tried putting a password on the BE database, which certainly stops prying eyes, but when I try to do anything from the FE, I get error message of

“Not a Valid Password”

“Microsoft Office Access cannot follow the hyperlink to …..”

Looks like I need to do something like name the BE password in the FE db ?

Thanks,

Graeme
Reply With Quote
  #2 (permalink)  
Old 02-08-12, 15:17
dave0810471 dave0810471 is offline
Registered User
 
Join Date: Jan 2012
Posts: 87
Graeme,

Others may disagree but if you want to remain with a file password solution, I would only protect the BE as the tables are the most important thing in any DB. I would convert the FE to MDE to secure it. Once you have done this you will probably have to re-create the link tables. Delete all LINK tables out of the FE then re-create the links (you should be prompted for the BE password). Using the linked table manager won't be any use as you need to re-create the links not refresh them.

Alternatively I would recommend using a workgroup security model rather than a database password. If you split a database into FE and BE (as in your case) the linked tables in the FE will adopt the same workgroup security rules as applied to the BE. This is also worth a look 10 tips for securing a Microsoft Access database | TechRepublic
I would however emphasise the importance of reading around the topic 'User level security' to ensure that your DB is completely secured. The use of a custom workgroup information file can be tricky. I would backup the FE/BE and system workgroup file just in case.

Hope this helps,
Dave
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On