The simplest way of making users and permissions on access 2007

[Pusher]

Hello all,
I’m new to access 2007 and I was looking on this and other forums and gathered that access 2007 does not have user and permissions because of some security issues. Can some1 please tell me the simplest way of making users and permissions on my DB so that only I can change the design and only some can use the forms and reports. It would be nice if I hade some logs of usage but not really needed. I say again the simplest way so I can implement it easily

 

[Trevor G]

Is your database a 2007 database or earlier version, if earlier you can still use the User Groups etc.

If 2007 then you could set up a table and assign permissions and then use DLookups on the start form to point to other forms where you would limit the access.

 

[Pusher]

Its a .MDB file (2002-2003 File format) but i used Access 2007 to create it. Also if you could give me a example DB of any solution you mention.

Thanks alot

 

[Trevor G]

Then you can customise the Quick Access Toolbar to add the UserGroup wizard to set up your UserGroups and Security side no problem, just add the icon.

Take a look at the attached has a module sheet which looks for the user and the autoexec which runs the module, there is a table called staff with Security Level added as numbers.

There are some basic forms to direct you on entry.

Hope it helps you out either way.

 

[Galaxiom]

Firstly to stop other changing the design, keep a master copy of the mdb where nobody else can touch it. Then distribute an mde file for their use.

Trevor's security is addrssing a different issue of access to to opening the forms. It will keep out the honest people but it has some easy vulnerabilities depending on how it is implimented.

The user could open the form directly using the navigation pane or VBA.

They could open the table and change their security level. You certainly would not use a linked table to hold that data. A connection via a recordset to table in another database done via VBA would be better.

Better to hold that table in MS SQL Server (or the free Express version).

They could change the username environment variable on their machine. It is a much better practice to make an API call and get the actual username.

 

[Pusher]

This example doesn't work here... Action failed Error 2950
All if need is to keep the honest people out - no one will try to hack it like that here - there is no sensitive information in it. All I want is to log usage for 5 people that only can enter the main form
maybe 2-3 people that can enter and see specific reports.