Access User Level Security

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an Access database that is located on a network share drive. I set up
Full Data User Level security, added all the users and gave them passwords.
Set up myself as Admin with a password. I did this all on my desktop. When
I go to the other user's desktops and test, I'm getting the following error
message: "You don't have the necessary permissions to use the <name> object.
Have your system administrator or the person who created this object
establish the appropriate permissions for you". How do I make this database
available to other users on their desktops? Thanks!
 
Ensure that the workgroup file is on the network. The shortcut referencing
the database and the workgroup file may be on the network or may be
distributed.

Distribute the front end, though this is not raising the error. Users must
also have appropriate permissions on the network.
--
***************************
If the message was helpful to you, click Yes next to Was this post helpful
to you?
If the post answers your question, click Yes next to Did this post answer
the question?
 
Sorry, I'm not following you. I'm getting that error message on other user's
desktops, not mine. Also, if I go to Windows Explorer and open the database,
it opens with no error message, but unfortunately, with no user-level
security. I believe I need to put a shortcut file, Shortcut.mdw on each
user's computer but I'm not understanding how to do that. I'm looking at
"The 10 Steps Summarized"; and I'm confused. It works fine on my desktop;
now I need to do something to each user's desktop and that's where I'm
getting stuck. I'm on Access 2002. Thanks!
 
eric said:
Sorry, I'm not following you. I'm getting that error message on
other user's desktops, not mine. Also, if I go to Windows Explorer
and open the database, it opens with no error message, but
unfortunately, with no user-level security.
Click to expand...

You should use the workgroup administrator to rejoin the standard system.mdw
that ships with Access. While joined to that, you shouldn't be able to even
open the mdb (it sounds like you haven't secure it properly). If you can,
then you missed a step in securing it.

Once you have it secured properly (so that you must be using the secure mdw
you created), then you'd put this secure mdw on a network folder, along with
the backend mdb (you should split the mdb and give each user a copy of the
frontend on their PC, linked to the backend on the server).

Then create a desktop shortcut with the following in the target...
"path to msaccess.exe" "path to frontend" /wrkgrp "path to secure mdw"
 
Back
Top