Process of creating user account & password for ms access database

[moonrb]

Hi.......i want to create two account & password for my access database. One account should have the right for operate the db & edit data only in case if wrong data posting but cannot delete the record or data. Other account should have all the rights including design changing of the db (that is me).

Plz give the proper suggestion.

[CJ_London]

What version of access are you using? if 2003 or earlier you can use the access security facility, if later you need to write your own

[moonrb]

yes i am using access 2003. i do not know how to use "access security" plz explain.......

[CJ_London]

Would love to advise, but I haven't used it for years. Search on line for Access 2003 user level security

Here are some links that may help

http://office.microsoft.com/en-gb/ac...005188226.aspx

http://www.pcreview.co.uk/forums/set...-t3880204.html

[zmbd]

MoonRB:

Access is not the most secure database out there... you may need to look at a more "grown-up" version if security is very important as there are very well known exploits that allow the more savvy user to bypass the userlevel security.

Additionally, unless you encrypt the database, please be aware that all someone need do is open your database in ACC2007 or ACC2010 and all of the user level security is stripped from the file once saved to the ACCDB format. Furthermore there are ways of moving this altered data back into the "secured" ACC2003 file.

- Split your database.
- At least, password protect the backend. Relink your password protected tables if needed in the frontend.
- Think about encrypting the data in the backend too.
- Think about encrypting the data in the backend too.
- Password protect the VBA project and protect from viewing.
- From the VBE make sure you do a final Compile.
- Make a copy of the *.MDB that has your frontend.
(I usually add a general password to this copy. Yes, everyone in the lab knows the password; however, it's like having the key to the outside door of the building; however, you may not have any keys that open anything else within the building. I've also rolled out new frontends with new password when a person leaves).
- Using this copy, make the compiled *.MDE version of the frontend for distribution. This will keep people from altering your frontend.
- For user level access, I've done it a few different ways...
use multiple backends in directory/subdirectories on the network. For these directories on the network I have had IT set the security so that only certain groups of people can read/write/modify files for certain directories and subdirectories. This way I can have IT manage the security some from the OS level too by adding/removing users from the authorized groups and I can add these groups to the directory security as I have admin privlages over the directory. This can be a pain to do and manage to make sure the data gets to places it needs to be (transactions are your friend). I also use mulitple forms that check tables with user ids (encrypted) against a form name, and so on...

I know that I'm missing something else here... it'll come to me on my walk across the jobsite.