Permissions

  • Thread starter Thread starter Mark Kobulnick
  • Start date Start date
M

Mark Kobulnick

I am an ADMIN, Full Permissions and User. I used the "user
level security wizard" on a database on my hard drive. I
had 2 Update data users and 3 read only users. I tested
each account and it was fine. When I moved the database to
a shared drive, and tried opening the database at a users
desktop that had authorization to the shared drive I
received the message, "You do not have the necessary
permissions to use the 'Room Utilization Database.mdb
object'. Have your system administrator or the person that
created this object establish the appropriate permissions
for you."
It looks like the Windows NT permissions are OK. As soon
as I try to access this database from another workstation,
I receive the error. Am I missing a workgroup or security
file on the other workstations? Help!
 
Actually the message you are getting is good! It shows that your database
has been secured properly.

You need to also copy the workgroup file to the shared folder. When you ran
the wizard it created a workgroup file on your computer - copy it to the
share.

If you can't find it, right-click the desktop shortcut on your computer and
look at the target in the properties. It will have something like

/wrkgrp "somepath\whatever.mdw" at the end
That's the path to the mdw.
 
Joan:
I found the file, "Secured.mdw" I opened it and saw
the users I created in "MsysUserList". I copied it to the
shared drive but I still get the message. Do I need
to "point" to the workgroup file on the shared drive? Any
thoughts? It opens on my PC but no others. It must be
looking in my C: drive.
 
Yes you need to give each user a desktop shortcut that looks like
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secured.mdw"

Note that you can use a UNC path names in the above i.e.
\\server\share\path\secured.mdw

One other comment I'll make. If you are going to have multiple users
hitting this database, you would be wise to split it. The backend
(tables/relationships only) will be located on the server. The frontend
(all other objects), contains links to the backend. A copy of the frontend
is put on each users computer. You'd then modify their shortcut to
"path to msaccess.exe" "path to frontend on local machine" /wrkgrp "path to
secured.mdw on server"

There is a database splitter that will do this for you, but since it's
already secured. I'd recommend you split manually.

Make a copy of the database (I'll call it BE.mdb) - Open this and delete all
objects except for the tables. Open the original (I'll call it FE), and
delete all the tables; then go to File, Get External Data, Link and locate
the BE.mdb (recommend you use Network Neighborhood to do this), select all
the tables and link.

Then just copy this frontend and the correct shortcut to each computer.

Why split? Because you'll reduce the chances of corruption, and you'll be
able to make design changes in your copy of the frontend without
interferring with the user's copy. Once the changes are complete, you can
copy the updated frontend to each user.

There are methods to automate this updating. See Tony Toews' site for one
example. Look for frontend updater at
http://www.granite.ab.ca/accsmstr.htm
 
Back
Top