Securing Access Databases part 2!

[afryer]

Hi All,

I have posted a couple of questions recently regarding securing my access database and have managed to get part of the way, but I have come accross one last problem that someone might be able to help me with.

I am using a bespoke workgroup file to connect to the database, using a command line to specify the workgroup file. This works fine when the desktop icon is double-clicked, the login prompt etc is displayed correctly. The only thing I need to do now is prevent the user from logging in using the default System.MDW file (i.e. double clicking on the database name and logging in with no authorisation)....nice easy task I thought!

My method of doing this and I am sure someone can tell me where I am going wrong with this....

- Double click on the application database, database opens as expected.
- Click on the Tools Menu, Security, User and Group permissions
- In this dialog there is only one user Admin, so I have removed all the privileges from this user, restarted the database and fully expected a message to appear saying you couldn't log on. It didn't.
- I then went into the groups section and removed privileges from the groups. This worked in a fashion, I couldn't logon by double-clicking the database, but nor could I logon using the workgroup file because some of the users in the workgroup file are members of the groups I disabled in the system workgroup. I also got a weird message about the database being "in an unexpected state".

Anyone any ideas on where I am going wrong here? I thought it would be a nice easy task, but it is proving to be anything but!

Thanks in advance


Andrew

 

[jsteph]

Andrew,
If the mdb is properly secured, it is impossible to open the .mdb with the default .mdw file. Bottom line--you need to remove admins group from all object access--including the 'database' object (at the top of the dropdown in the permissions dialog). Then in your 'secured' mdw, you have a new group and or users with your chosen object permissions.
--Jim

 

[Ed2020]

To clarify what jsteph has said you need to remove all rights from the Admin user (rather than the Admins group) to your database. Also add a password to the Admin user to prevent users from using this account.

Ed Metcalfe.

Please do not feed the trolls.....