Database Locking down the users

[accessNator]

I have inherited a .MDB file. All of my users are on Access 2010. Can someone point me a reference area where I can prevent the USERS from manipulating the tables, queries, forms and macros and modules directly. All I want them to do is access forms and do the data entry from there.

Thanks.

 

[accessNator]

Just doing a quick lookup here are a few steps I have done so far. Open for suggestion and other tips as I continue on.

1. Create an new accdb file importing all contents from the .mdb file
2. Hide the navigation pane and ribbon bar
3. Split Database so I have an .accdb and *_be.accde file
4. Create password for .accdb file
5. Create .accde file from .accdb file.

Thanks.

 

[accessNator]

Anybody care to add suggestions?

 

[DavidAtWork]

I'm not too familiar with Acess 2010, but if you create the equivalent of a .MDE frontend file and have the database window hidden, disable the bypass keys (all this can be set using vba in a module that can be run by an autoexec macro on start up) and set a password in the project properties. That will prevent users from accessing the database objects and making changes. an MDE file doesn't allow users to see the code or get to the design view of forms.
Of course for your own use, you need to design a method of getting into your version of the database which will be the original .MDB file for when you need to make changes or further development. When you've finished your changes, create a new .MDE and distribute.
David

 

[accessNator]

I'm not too familiar with Acess 2010, but if you create the equivalent of a .MDE frontend file and have the database window hidden, disable the bypass keys (all this can be set using vba in a module that can be run by an autoexec macro on start up) and set a password in the project properties. That will prevent users from accessing the database objects and making changes. an MDE file doesn't allow users to see the code or get to the design view of forms.
Of course for your own use, you need to design a method of getting into your version of the database which will be the original .MDB file for when you need to make changes or further development. When you've finished your changes, create a new .MDE and distribute.
David

Thanks for your reply. I did a few of those suggestions. I knew there was a couple of more that I missed.