Re: Creating security for MS Access application

On 11 Jul 2006 09:28:39 -0700, PadmaBhaskar@xxxxxxxxx wrote:

I have a MS Access application which would be on the network and
multiple users must be able to access using their respective used ids.
I wanted to create user ids and grant permissions based on user ids.
First, I created a workgroup using Tools -> Security -> Workgroup
Adminstrator. I created user accounts and set permission level to
tables, queries etc.

Now, the issue is when I try to open some other MS Access application/
MDB file, it asks for the user name, passowrd. All the security
settings seem to be done at a global level on my computer.

You've "joined" your workgroup file on your machine, and obviously the Admin user has a non-blank password, which is why
all Access apps are prompting for login. Find and rejoin your default System.mdw file and the login prompts should stop.

The other
problem is, when I access my application from a different computer, it
does not ask for any user id, password. So, the database is not
ultimately not secure.


You've not properly secured your database if that's the case. With a properly secured database, you would get the
standard "You don't have permissions blah blah" message. I'd strongly encourage you to read up on the proper application
of User Level Security before mucking around with it too much more. Also, make sure to experiment on a COPY of your
database (best to keep a good copy off-machine, on a network drive or USB stick).

When you do finally get your db correctly secured, you'll need to place your workgroup file on a network-accessible
drive/folder, and "point" your users to it. This is usually done with a shortcut on the user's desktop, the Target of
which is something like this:

"Full path to MSAccess.exe" "Full path to your db" /wrkgrp "Full path to the workgroup file"

The MS Access Security FAQ:
http://support.microsoft.com/default.aspx?scid=%2Fsupport%2Faccess%2Fcontent%2Fsecfaq.asp

Joan Wild's page, with instructions on how to properly secure a database without the Security Wizard:
http://www.jmwild.com/Accesssecurity.htm

Lynn Trapp's page, with more info on security:
http://www.ltcomputerdesigns.com/Security.htm

Jack MacDonald has a great paper explaining what ULS is and how it works
http://www.geocities.com/jacksonmacd/

Scott McDaniel
scott@xxxxxxxxxxxxxxxxxxxxxxxxx
www.infotrakker.com
.

Relevant Pages

  • Re: Creating security for MS Access application
    ... security settings seem to be done at a global level on my computer. ... You've "joined" your workgroup file on your machine, ... You've not properly secured your database if that's the case. ... with instructions on how to properly secure a ...
    (microsoft.public.access.security)
  • Re: Creating security for MS Access application
    ... security settings seem to be done at a global level on my computer. ... You've "joined" your workgroup file on your machine, ... You've not properly secured your database if that's the case. ... with instructions on how to properly secure a ...
    (microsoft.public.access.security)
  • Re: A note to add to ASPFAQ.com for database compacting
    ... I set the database directory permission to give full access to ... then checked "Allow inheritable permissions from parent to ... Thus your problem is that you have to high of security set ... > the files needed and also a compact & repair operation will not cause ...
    (microsoft.public.inetserver.asp.db)
  • Sorting out security
    ... MS Access security. ... created a new workgroup, added a password for the Admin role, added groups, ... user IDs and passwords for users and allocated permissions on the ... remote logins to a secured database. ...
    (microsoft.public.access.security)
  • RE: Security setup does not allow import of tables
    ... When you click on the menu option Tools> Security> User and Group ... Permissions at the bottom of the screen does it show you logged in as the ... | new system database that has a unique Name, Organization, ... In the User and Group Accounts dialog box, ...
    (microsoft.public.access.security)
Loading