New user has no permission to open db

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

Guest

I have been working with Access 2k for quit a while and I had a strange thing
happen today, I added a new user just as I always do "Tools", "Security users
and Groups", then "New". I enter the user name and id and then select the
group(s) I want them in, same as other users. when I try to log them into the
data base to set the password I get the following error: "You do not have
the necessary permissions to use the 'H:\workstation\workstationmdb.' object.
Have your system administrator or the person who created the object establish
the appropriate permissions for you." I am the system administrator and
creator of the DB. I have checked all permissions on the new user and they
have the same permissions as several others in the office (who work fine). I
cannot figure out what is going on. Thanks in advance for your assistance.
jmillerwv
 
How is this 'user' opening the database? They should have a desktop
shortcut with the following in the target:
"path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw"
 
Thank you for your reply. The user is opening the frontend same as all others
through a short cut on the desktop. It points to the frontend located on
their drive and the tables are linked to the data located on a server. I have
found what I believe is the problem the groups that the user was assigned to
did not have permission to the database. The funny thing is that other users
are assigned to the same groups and they could log in just fine, but when I
added the new user they were unable to log in. I know when I orginally set up
the groups and the permissions on the groups,I had given database access on
the user account and an account I created called data entry. When I found the
solution finally I found that the database permissions were gone on both the
groups. I cannot figure why it would loose the permissions I had set
orginally. Again thanks for your assistance. for now it is fixed. I will try
to figure out why it lost the permissions.
jmillerwv
 
If you, at any point, created a new mdb and imported the objects from your
secure mdb, the permissions won't import. That could be one source.

Another possibility is that you are dealing with multiple copies of the
frontend (the permissions are stored in the mdb file). You have to use a
single development mdb, and ensure all changes are made in it. Then
distribute the update, overwriting the users' frontends.
 
Joan,
Thank you for your responses. The way our system works when a user logs into
the network at anytime there is a script that runs to copy the frontend (.mdb
file) as well as the .mdw file from our server to their machine so that they
always have a current frontend with any changes I have made as well as any
security changes. At any time I can request that the users log off and log
back on to the network if I need them to get an important update to the db.
Your firts suggestion may be the culprit as I have been working on updating
the db to a newer version. It may have happened in one of those tries. I do
thank you for all your assistance, and thank you I have learned something
today and am greatful for your assistance.
jmillerwv
 
You're welcome. Copying the frontend would not lose permissions, however
importing would. It sounds like that could be the source.

Also it isn't necessary, nor adviseable to copy the mdw to them in your
script.

If your users are able to change their password, the next copy from the
server won't have this change, since the passwords are stored in the mdw.
If they can't change the password, then I see no harm in copying it.

You can have their desktop shortcut point to the mdw on the server.
 
Back
Top