Using Access Built-in Security with a Front End/Back End

[dch3]

I've never implemented security, but have started looking at it due to a
project that I'm working on.

Since my concern is over the data in the table and not the objects, any
thoughts on just setting up a single common user account to allow access to
the data, but prohibit deleting records directly in the tables. I want the
users to only be able to delete a record from the forms that they have access
to but without the need to manage multiple users.

The final Front End will be an .MDE file with a custom menu bar that does
not give the user access to the DB window and with a custom Main Menu.

David H

 

[Chris O''''Neill]

I'm a neophyte with MS Access security, but I don't see why you can't do
that. Just setup the security as usual, and then just create one new user
account that has the permissions you desire. To keep the users from working
directly with the table(s), you'll need to use RWOP (Run With Owner's
Permissions) queries from within the application.

More info (including RWOP queries) is available in the MS Access Security
FAQ here:

http://support.microsoft.com/?id=207793

A really good summary of the basic steps required is here:

http://www.keithwilby.com/

Hope that's helped...

Regards, Chris