G
Guest
The questions:
1. Is it possible to create one (1) workgroup that is used by more that one
database with each database have different permissions for different grouping
of users?
(The shortcut method, while an option will get to be a big hassle to
maintain as more and more databases are added. I would prefer not to go
there if possible)
2. If it is possible, how can it be done if there are existing databases,
specifically, two with security (using their own mdw files), and one without
security (using the system mdw file)?
The full story:
The company I work for has a client that has created (or had created by a
third party) three Access (2003) databases:
One is unsecured, is used (and abused) buy most of the staff (25), and
uses the system.mdw
The second is secured, is used by just a few of the staff (6), and uses
its own workgroup file.
The third is secured, is used by just a few of the staff (6), and uses its
own workgroup file. It has not deployed…yet.
The third one I was asked to secure as I'm the only employee who admits to
having used Access - that was 4 years ago (2000 was the last version).
After several days of researching security and experimenting with setting up
security on a copy of the client database at my office, I was ready to go to
the client and setup the security.
All went well. Well, not quite. Ended up with dueling workgroups.
Retreated to the office for further research and experimenting.
I know the shortcut with the workgroup method will work, but as more
databases are added, with more and more users, that would end up being a
maintenance nightmare at some point. As I'm going to be the guy doing the
maintenance, I'm looking for alternatives.
My research seems to indicate it is possible to create one workgroup used by
all the databases, current and new. Unfortunately, have not found a clear
description of how to do that, and absolutely nothing on how to do that when
there are already existing databases.
1. Is it possible to create one (1) workgroup that is used by more that one
database with each database have different permissions for different grouping
of users?
(The shortcut method, while an option will get to be a big hassle to
maintain as more and more databases are added. I would prefer not to go
there if possible)
2. If it is possible, how can it be done if there are existing databases,
specifically, two with security (using their own mdw files), and one without
security (using the system mdw file)?
The full story:
The company I work for has a client that has created (or had created by a
third party) three Access (2003) databases:
One is unsecured, is used (and abused) buy most of the staff (25), and
uses the system.mdw
The second is secured, is used by just a few of the staff (6), and uses
its own workgroup file.
The third is secured, is used by just a few of the staff (6), and uses its
own workgroup file. It has not deployed…yet.
The third one I was asked to secure as I'm the only employee who admits to
having used Access - that was 4 years ago (2000 was the last version).
After several days of researching security and experimenting with setting up
security on a copy of the client database at my office, I was ready to go to
the client and setup the security.
All went well. Well, not quite. Ended up with dueling workgroups.
Retreated to the office for further research and experimenting.
I know the shortcut with the workgroup method will work, but as more
databases are added, with more and more users, that would end up being a
maintenance nightmare at some point. As I'm going to be the guy doing the
maintenance, I'm looking for alternatives.
My research seems to indicate it is possible to create one workgroup used by
all the databases, current and new. Unfortunately, have not found a clear
description of how to do that, and absolutely nothing on how to do that when
there are already existing databases.