Strange situation on a new computer

[Anne]

I installed access on a new workstation. I connect to both the server and
the workstation via PCAnywhere.
The access database is linked to security.mdw and resides on the server,
along with the backend. I put the frontend also into the same location for
the purpose of copying it to the user's computers.

I double checked and the FE it is linked to the Security.mdw on the server.
When I copy the front end from the server to the workstation it shows the
user and group permissions as locked and the workgroup administrator does
not even show. Therefore I cannot join any other workgroup. I logged into
the workstation with my name, the one who ownes the database. When I check
the user and group accounts, I can see, that the database must now be linked
the the default microsoft system.mdw because there are no users, except
admin and user. I tried putting the security.mdw into the shortcut, but that
did not help. The security is locked.

I copied the same FE to another workstation tonight and without a problems.
I cannot figure out, why I cannot get this workstation to work.
I am the administrator of the entire network. I logged into the workstation
with my name and I have access to everything on the server, so I don't think
it is a windows security issue.

Cannot figure out what is happening here. It is not a matter of lost
security. Why can this be happening?
Help,
Anne

 

[Rick Brandt]

I installed access on a new workstation. I connect to both the server
and the workstation via PCAnywhere.
The access database is linked to security.mdw and resides on the [snip]

Stop right there. There is no "link" between a workgroup file and an mdb. You
use a particular workgroup file when you open Access. This is either a
workgroup that is specified as a command line argument or it is the user's
default workgroup as set by the workgroup admin utility. All of this is
estabished BEFORE Access attempts to open any particular mdb file.

So...how are you specifying the correct mdw? And if you're not and the file is
still opening then you didn't secure it properly. When secured properly only
the correct workgroup file should allow you to open the file. This despite the
fact that there is no "link" between the two.

 

[Anne]

I don't know what I did, but with the new shortcut to the security.mdw now
works.
So you mean I did something right without knowing it?
The workgroup administrator, which is not showing up on this workstation is
not supposed to show up on a secured database? It is showing up on all the
other workstations.
I set up another workstation tonight, which was very similar in the setup to
the one I had trouble with, but the workgroup does not show up locked.
Anne

I installed access on a new workstation. I connect to both the server
and the workstation via PCAnywhere.
The access database is linked to security.mdw and resides on the [snip]

Stop right there. There is no "link" between a workgroup file and an mdb.
You use a particular workgroup file when you open Access. This is either
a workgroup that is specified as a command line argument or it is the
user's default workgroup as set by the workgroup admin utility. All of
this is estabished BEFORE Access attempts to open any particular mdb file.

So...how are you specifying the correct mdw? And if you're not and the
file is still opening then you didn't secure it properly. When secured
properly only the correct workgroup file should allow you to open the
file. This despite the fact that there is no "link" between the two.

 

[Rick Brandt]

I don't know what I did, but with the new shortcut to the
security.mdw now works.

Getting prompted and having the file open when you use the correct MDW file is
only half of setting up security. The other half is that when you do not
specify the correct MDW file you should NOT be allowed to open the file
(prompting or no). Is this the behavior you get?

So you mean I did something right without knowing it?
The workgroup administrator, which is not showing up on this
workstation is not supposed to show up on a secured database?

I don't know what you mean by this. The workgroup administrator is a utility
that is used to change your default workgroup and to create new workgroup files.
It should be available on all PCs that have Access installed.

It is
showing up on all the other workstations.
I set up another workstation tonight, which was very similar in the
setup to the one I had trouble with, but the workgroup does not show
up locked.

"...the workgroup does not show up locked" also makes no sense to me. What do
you mean by this?

 

[Anne]

When one click on security the following menu items normally show up:
Set database password
Workgroup Administrator
User & Group Permissions
etc

All the workstation I have set up so far (except the one last night) , the
menu item "Workgroup Administrator" shows up as menu item. On this one
computer last night, this line item does not appear and the line "User &
group Permissions" shows as locked, even with the shortcut pointing to the
correct MDW.
When it did open the FE with the default access.exe it did let me into the
database and showed me all the files, although I could not change anything.
I think something has gone haywire on this computer, because it would asked
me for a user name and password in my security.mdw, but when I looked at the
security, the only users admin and users.
Anne

 

[Rick Brandt]

When one click on security the following menu items normally show up:
Set database password
Workgroup Administrator
User & Group Permissions
etc

All the workstation I have set up so far (except the one last night)
, the menu item "Workgroup Administrator" shows up as menu item. On
this one computer last night, this line item does not appear and the
line "User & group Permissions" shows as locked, even with the
shortcut pointing to the correct MDW.

The Workgroup Administrator utility used to be a separate utility instead of
being available as a menu item inside Access. Does this one computer have
an older version of Access?

When it did open the FE with the default access.exe it did let me
into the database and showed me all the files, although I could not
change anything. I think something has gone haywire on this computer,
because it would asked me for a user name and password in my
security.mdw, but when I looked at the security, the only users admin
and users.

Then they are opening it with the wrong MDW file which means that your
security is not correct. When using the wrong MDW file they shouldn't be
able to open the file at all.

 

[Anne]

Now that I have made major changes to the security, setting up my own
groups, I need to test this on the various computer.
I will keep you up on the progress. It has been a long day. Give me another
day to get this set up properly and I will advise on the results.
Learned a lot reading up on various website about security setup and I made
major changing the way I was doing this.
To answer at this point one of your questions, this one odd workstation does
have an older verions of access, which is 2000, where all the other are
using 2003.
It has been along day, but I am glad to you are sticking with me on this. I
need to figure out the right way to do thing and I think I have gotten an
whole new eduction on the security aspect of access. I just can't cope with
it tonight. My brain it just not working tonight.
Thanks for your help. I will update this tomorrow, when I am thinking more
clearly.
Thank again,
Anne.