"Access denied" message when joining workgroup

[Guest]

Why would a user get an "access denied" message when attempting to join a
workgroup? The user has a name and password already set up in the database;
coding the workgroup name into the properties for the shortcut to the
database gets him in okay; but our protocol is that the database workgroup is
a user's primary workgroup, and I can't get this user set up that way. The
workgroup file is on a network folder to which the user has full permissions.
I've never run into this before. Any ideas?

 

[Joan Wild]

Why would a user get an "access denied" message when attempting to
join a workgroup? The user has a name and password already set up in
the database; coding the workgroup name into the properties for the
shortcut to the database gets him in okay; but our protocol is that
the database workgroup is a user's primary workgroup, and I can't get
this user set up that way. The workgroup file is on a network folder
to which the user has full permissions. I've never run into this
before. Any ideas?

As I understand it, you are getting this message when trying to use the
workgroup administrator. It's the wrkgadm.exe file that they don't have
permission to use.

 

[Lynn Trapp]

As I understand it, you are getting this message when trying to use the

workgroup administrator. It's the wrkgadm.exe file that they don't have
permission to use.

Joan,
I encountered that same problem here a few years ago and we found out that
each user had to be an administrator of their PC in order to run the work
group administrator. The company policy had changed so that no one was
allowed to be an administrator on their computer, so our tech guys had to go
to each machine and join the workgroup for the user.

 

[Joan Wild]

Joan,
I encountered that same problem here a few years ago and we found out
that each user had to be an administrator of their PC in order to run
the work group administrator. The company policy had changed so that
no one was allowed to be an administrator on their computer, so our
tech guys had to go to each machine and join the workgroup for the
user.

That makes sense to me. I think that being a member of Power Users would
have been enough though. I have not encountered the problem as a Power
User, but Users group did.

 

[Guest]

This explains everything. Thank you VERY MUCH for the help.

 

[Guest]

I have a similar situation. However, the user does not have a problem
opening the wrkgadm.exe application. The "Access denied" error shows up
after they point to the shared .MDW file on the network. The network
permissions have been confirmed. Other users have been able to join the .MDW
file using a computer with MS Office Pro 2003 but not on the computer with MS
Office Pro 2000. Is there any issues with backward compatibility for
security databases created using MS Office Pro 2003 that would prevent
previous versions from joining them?