Can you use the same workgroup?

  • Thread starter Thread starter Ted
  • Start date Start date
T

Ted

I have created a workgroup to use for security permissions
other than the default SYSTEM.MDW. I am wondering whether
it is good or bad practice to use this new workgroup for
multiple database security or should I create different
workgroups for each database?
Thanks in advance.
 
Hi, Ted.
Can you use the same workgroup?
Click to expand...

Yes. One can use the same workgroup for multiple Access databases.
I am wondering whether
it is good or bad practice to use this new workgroup for
multiple database security
Click to expand...

It depends upon the situation. For example, if an organization has two
departments -- the finance and the shipping/receiving departments -- using
Access database applications, then these should probably use separate secure
workgroups, since a shipping clerk probably shouldn't be able to log into a
database application that is used solely by the finance department.

However, if the finance department and shipping/receiving departments are
sharing the same database application, then both departments should be using
the same secure workgroup.

The number of concurrent users might also be a concern. Even a workgroup
file is an Access database file, so it's handled by Jet. Jet can handle up
to 255 concurrent users in each database file. But to be honest, it's very
unusual to have this many concurrent users logging into multiple databases
from the same workgroup.

From a developer's point of view, though, fewer workgroups are easier to
maintain than many workgroups.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
It depends upon the situation. For example, if an organization has two
departments -- the finance and the shipping/receiving departments -- using
Access database applications, then these should probably use separate secure
workgroups, since a shipping clerk probably shouldn't be able to log into a
database application that is used solely by the finance department.
Click to expand...

Gunny,
I would recommend using the single workgroup information file, even in the
scenario you mentioned. If the people in the shipping/receiving group should
not be logging into the finance department's database, then the workgroup
security can be set to not give them Open/Run permissions on the database.
As you mentioned later, trying to maintain multiple workgroup information
files can be a big hassle, to say the least.
 
Back
Top