M
miaplacidus
I think I understand. The mdb file contains the
permissions. The workgroup file contains the usernames and
passwords.
When Access opens it picks up the username and password
from the workgroup file. Then when the mdb file opens it
applies the permissions as identified by the username and
password.
I still have some questions.
1) I don't see in the workgroup administrator anything
about a default workgroup. I can either join a workgroup
or create a new one. If I join a new workgroup, does that
then become the default?
2) If I put my mdb out on the shared drive, does this mean
that I have to go to each user and put the shortcut on
their machine to direct them to the right workgroup? If I
do that, what prevents them from just switching back to
the default workgroup, system.mdw? What prevents them from
navigating to the MDB file and opening it without the
shortcut? As I see it, no shortcut, no security.
3) If they do that then the administrator will have no
password and they can get right in. Is that why you have
to take Admin out of the Admins group and have admin be a
user? Even though I did that, I now have a situation where
the mdb is on the shared drive and I have to log in, other
users (still using their default mdw file) can go right in.
4) Is there no way to administer the security of a file
that is on the shared drive from a central location so I
don't have to physically visit each user to determine what
the proper strings are for the shortcut?
5) As a newbie I apparently did not write down the strings
when the user group was first created. I still have my
passwords so I can get in OK. I have made changes to
the .mdb file which I would like not to have to redo. Now
that I think I understand the security process I would
like to make an unsecured copy of my file to use for
continued development. Then when I create a new object, or
whatever, I can copy it to the secured file. In the
meantime I would like to strip all the security from my
current file, copy it to my development file, and then re-
create the security properly (and record all the strings).
as I understand it, I do not need the original strings to
do this, only a working admin password. Is this correct?
-----Original Message-----
permissions. The workgroup file contains the usernames and
passwords.
When Access opens it picks up the username and password
from the workgroup file. Then when the mdb file opens it
applies the permissions as identified by the username and
password.
I still have some questions.
1) I don't see in the workgroup administrator anything
about a default workgroup. I can either join a workgroup
or create a new one. If I join a new workgroup, does that
then become the default?
2) If I put my mdb out on the shared drive, does this mean
that I have to go to each user and put the shortcut on
their machine to direct them to the right workgroup? If I
do that, what prevents them from just switching back to
the default workgroup, system.mdw? What prevents them from
navigating to the MDB file and opening it without the
shortcut? As I see it, no shortcut, no security.
3) If they do that then the administrator will have no
password and they can get right in. Is that why you have
to take Admin out of the Admins group and have admin be a
user? Even though I did that, I now have a situation where
the mdb is on the shared drive and I have to log in, other
users (still using their default mdw file) can go right in.
4) Is there no way to administer the security of a file
that is on the shared drive from a central location so I
don't have to physically visit each user to determine what
the proper strings are for the shortcut?
5) As a newbie I apparently did not write down the strings
when the user group was first created. I still have my
passwords so I can get in OK. I have made changes to
the .mdb file which I would like not to have to redo. Now
that I think I understand the security process I would
like to make an unsecured copy of my file to use for
continued development. Then when I create a new object, or
whatever, I can copy it to the secured file. In the
meantime I would like to strip all the security from my
current file, copy it to my development file, and then re-
create the security properly (and record all the strings).
as I understand it, I do not need the original strings to
do this, only a working admin password. Is this correct?
-----Original Message-----