User Accounts for Access 2007

[Steven.Ashby82]

Good Morning All,

I'm sure this has been asked in various levels but I haven't been able to find an answer suitable for my needs.

I have created three databases and until now I have managed them by disabling options within the "Access Options" menu and subsequently entered the databases by using the shift function.

However one of the three is to be made more widely available and I need to tighten the controls available to both them and myself.

The database is on a shared network drive in which I do not and can not obtain admin rights.

Any help and suggestions are desperately and greatly needed

 

[CJ_London]

Consider converting the accdb to a accde which will protect the code and form/report objects but not tables and queries.

Have you created a front end/back end, if not this is also recommended - you can then password protect the back end which will protect the tables from design change.

This leaves queries - If you don't have one already you will need to create a user table for users to login with a password and control access rights that way.

One way of hiding objects is to prefix them with Usys and they will then be treated as system objects so if your show system objects is false they will not be visible (as opposed to show hidden objects)

 

[Steven.Ashby82]

Thanks CJ I really appreciate your help, is there any examples out there of these points?

 

[CJ_London]

plenty

just try searching on

'create accde' - and is easily done - compile db then File>save and publish as accde

'front end back end'

'user access' and similar

 

[Pat Hartman]

You can hide tables and other objects without prefixing them with USys which at this point would be a lot of work I am sure. Just set the hidden property to true.

Look for "disable shift bypass" for code to disable the shift as a way of getting into the database in design view. Keep in mind that implementing this is tricky so make sure you have at least three separate backup copies should you succed in locking yourself out also.

Finally after creating the .accde (again don't loose your .accdb, you can't go back to make changes without it), rename the extension to .accdr. This tells Access to "pretend" to be the runtime engine even when it isn't.

Except for the shift-bypass which is more difficult, a knowledgeable user could easily circumvent the other steps. The best you can do is keep out most users and make it difficult for the more knowledgable.