Need article on protecting a database from end users 1

[BallunarCrew]

I am looking for an article or whitepaper describing steps to take to protect an Access 2007 database from the end users. I want them to have a form (like a menu) that has buttons that will open other forms where they enter and save data. I do not want them being able to do anything else. I know I can create a custom ribbon but I need some way to get into design view and other parts of the DB when I need to that they can't or don't know about, I don't want them to be able to use the Shift key to bypass start up options, I don't want them to be able to right click and go to design view, etc.
I am thinking someone has probably already written a detailed description of things to consider - maybe some shortcuts I do not know about. I can look all this up myself and do a lot of testing but if someone has already invented this wheel, then I would like to share in the knowledge. I tried searching the web and keep finding articles on securing databases but securing the server or network they are on - this is on the wrong track. Thanks in advance.

 

[MajP]

http://msdn.microsoft.com/en-us/library/bb421308(v=office.12).aspx

If you google there are plenty of docs. Top ones

1)Split the database
2) make the front end an mde, accde
3)disable shift bypass (google)
4)make forms pop up and modal
5)limit the menus
6)hide objects

 

[Gammachaser]

Remember that disabling the shift key only limits access to those that are not familiar with how to re-enable it. I wrote a small program designed to set the start-up options from outside of a database so that I could manage multiple databases that I had written. Once I was done I realized I had created a tool that not only could manage my databases, but could also unlock databases I had not written, and lock them even if I didn't own them and they had not been locked before. I decided not to distribute it because it could be used maliciously.

 

[Andrzejek]

I know this is an Access forum, but have you consider moving to other data bases, like SQL Server, MySQL, or ORACLE? And writing your app in VB or VB.NET?

I have over 600 users, app written in VB 6 and none of my users have any idea where my data base (ORACLE) is and how to access it other way than my app.

Looks like you want security of your data, this is one way to go.

Just my $0.02


Have fun.

---- Andy