password for backend database

[mazza]

I am using a database with a front end with tables linked to 2 back end tables.

The front end database is protected by a password, however I also want to protect the backend databases using the standart password protection in MS Access.

I want to protect the backend from being opened, unless users use the front end (if that makes sense)

The problem is however that as soon as I open the front end database it tells me that it cannot open or read the tables, linked to the password protected backend(s).

is there a code I can use that the frontend can use the password protected databases?

 

[ghudson]

Break the table links in your front end. Open the backend and set your on open database password and then close it. Reopen the front end and relink your tables. You will be asked for the password and it will be stored in the link to the tables in the password protected backend. The user will never be asked for the password as long as the links are not broken.

You should know that there are many freeware programs in cyber space that will easily crack the on open database password. True Access security with user workgroups and permissions is more secure and I have yet to see a "freeware" program that will crack Access workgroup security.

 

[mazza]

thanks

I know that a databse is easy to crack but using work groups is difficult if you are not a system administrator.
The program is also distributed to different sister company's each operating different operating systems etc.
I fear that distributing would be a more cumbersome process.

 

[MWChelle]

How Do I Protect Back End of Split Database?

Ghudson,

I am working in a multiple-user environment and have a database I wish to secure and split. I have successfully set up the security parameters using the workgroup. However, after I split my database, the back end (table) is left unsecured. How can I keep the back end protected so that users can not access it directly, but access it only by using the front end? The back end will be saved to a shared network drive.

Forgive my ignorance, as I am only 2-months old using Access and still learning.

I appreciate any insight you can offer.

-Michelle

 

[ghudson]

The way "I" do it is to make a copy of the db before spliting it. Then I delete everything but the tables to be shared in the back end copy and I delete the shared tables in the front end copy. Then I link the tables to be shared from the back end copy to the front end copy. You can use the same work group file you had already created before you split the db. Just change the target value of the secured shortcut you use to open the new front end. That way the security remains the same for both the front end and the back end.

 

[MWChelle]

How can I make a copy after the Dbase has been protected?

GHudson,

Thank you very much for your reply. This will be a tremendous help to me. I believe I understand what you are instructing me to do, however, at the risk of showing my ingnorance with the program, can you please tell me how I can make a copy of the database after it's been protected? I don't see where/how it gives me the option to do so.

Thank you again for your response.

-Michelle

 

[ghudson]

From Windows Explorer just use the old fashioned Copy [Ctrl + C] and Paste [Ctrl + V] Windows commands to make a copy of your database.