Securing a database

[jsic1210]

Hello,
I'm trying to secure my database so users can't edit tables, forms, reports, queries, etc. I want to know if I'm going about this the right way, and if so, what's the next step. I'm splitting the database, making an ACCDE for users:
1. I inserted code to disable the bypass key.
2. I inserted code to hide the Quick Access Toolbar (QAT) in the On_Load sub of the form that opens with the DB.
3. Deselect Navigation Pane, Allow Full Menus and Allow Default Shortcut Menus are deselected
4. Then, I use the immediate window to show the QAT, I then create an ACCDE.

How do I link this ACCDE with the original ACCDB? Am I supposed to delete tables from the front end and link the forms/reports to the back end DB?

Any suggestions/help is appreciated!

 

[RainLover]

Put the tables in the back end.

Create your relationships.

Password protect this Database being the back end.

Then link the front end to the back end tables.

You also need to disable toolbars etc in the back end.

Hope this helps a little.

 

[jsic1210]

It does, thank you. But it still leaves me with some questions. I don't know exactly how to go about these steps.

How do I "put the tables in the back end?" When I create the ACCDE, they are already there. Do I split the database, link everything, then make the ACCDE?

Re disabling the toolbars in the back end, how I do this? Do you mean disable the front end toolbars from the back end?

Also, when I want to edit/add forms and reports to the ACCDE, how do I do this?

Thanks!

 

[jdraw]

You have to do as Rain said. And you have to keep your ACCDB if you plan on making any edits/additions etc.

You should be using Google to find details of the whole process.

You can not edit an ACCDE, so you have to use the ACCDB you made the ACCDE from, keep it and protect it. You would make changes in the ACCDB, then recreate another ACCDE.

Google and Youtube can help you.

https://www.fmsinc.com/MicrosoftAccess/DatabaseSplitter/

http://pcsupport.about.com/od/fileextensions/f/accde-file.htm

Good luck

 

[RainLover]

This is a difficult thing to do. Securing a database that is. When you finish I will still be able to break in. Your regular users won't be able to. So you will end up with a Database that will keep out honest people and those who know nothing about this type of thing. Some people will be able to get in.

Is your Database complete? Because if you lock yourself out by converting to a ACCDE you will have no where to go. Remember to back up while under construction. On average back up every 5 minutes.

The Back end of any database is where the data is stored. It is shared by all users and is stored on the server. Wheras the front end is given to every user and is placed on their local machine.

If you convert the completed front and back ends you can create a link in the front end to the back end before distribution of the front end to each user. You will need the password in order to link to the back end. You will need to enter this when linking and from there the front end will remember.

Cheers

 

[jsic1210]

Thank you both very much for your help!

In my case, the front end database is stored on a shared drive, rather than each person's desktop. If each user saved it to his desktop, would the data still save to the back end database on the shared drive?

Also, I make frequent changes to the database. Isn't it inefficient to keep saving my updates (almost daily) to the users' desktops?

 

[RainLover]

What I suggested is what I do, and have done for many years. So does every experienced Access programmer. This method prevents things like corruption.

You could try doing a Google on sharing a database to find out more.

 

[RainLover]

Re disabling the toolbars in the back end, how I do this? Do you mean disable the front end toolbars from the back end

I missed this one.

You will need to disable Toolbars in both front and back ends because they are totally separate databases.

I don't run Access past 2003 so I don't have code that I would feel safe passing onto you. However there should be something in the archives that will help.

The Navigation pane is the most difficult because it can be turned back on via a Function key. There would be a solution somewhere here at AWF.