Microsoft Access Security Best Practices when linking to a SQL back end

Tech-Archive recommends: Fix windows errors by optimizing your registry

tdmailbox_at_yahoo.com
Date: 02/09/05 

Date: 9 Feb 2005 12:10:03 -0800

Does anyone know where I can find a best practices type document on
access security? Basicly I have a access database application I am
writing with a SQL server back end for a bank client. The application
was originally written to use access's own .mdw file for security.

However there is a push by the internal IT staff for me to move the
security into a table inside the SQL database. I am not really sure
what advantages this would provide and I am trying to make sure I am
not missing something. They are not looking to premission each user on
the SQL database, they are looking for me to create a user table inside
the SQL backend for the database that I built and have the access
databse call that table to verify permissions before granting access to
the application.

I am trying to determine if there is any advantage to configuring
security that way rather then using a .mdw file.

Can anyone shead some light on why using an internal(or in this case
linked) table would be better to store user ids and password?

Relevant Pages

  • Re: MDE
    ... - You are using the incorrect MDW file used to secure the database. ... MDE open or not) select teh menu option Tools> Security> User and Group ... if you don't see the other User Accounts you created when the ...
    (microsoft.public.access.security)
  • Re: Whos in the .ldb first?
    ... If the .mdw file you secured the database with isn't there, ... good indication that your security wasn't set up correctly. ... >>have full permissions on the FOLDER that the database is ...
    (microsoft.public.access.security)
  • Re: security not requesting log in
    ... If you had done this, then no matter what mdw file she used, ... Another step you should have performed is to secure the database file. ... and delete all the security files and create a new file. ... opens immediately to the main screen and shows her as Admin. ...
    (microsoft.public.access.security)
  • Re: security not requesting log in
    ... If you had done this, then no matter what mdw file she used, ... Another step you should have performed is to secure the database file. ... and delete all the security files and create a new file. ... opens immediately to the main screen and shows her as Admin. ...
    (microsoft.public.access.security)
  • Re: setting a password on a button on the switchboard
    ... Could you send me the sample database for the fourth option (4. ... > Security in an Access database can probably be broken down into two big ... > points about being easier than User Level Security, ... > What type of data are you trying to protect? ...
    (microsoft.public.access.forms)