Workgroup file limit?

[AccessIM]

I have several databases attached to the same workgroup file. This makes it
easier for the users to remember only one password for several databases and
also makes setting security easier for me because I set permissions using the
groups contained in the workgroup file and the users are already assigned to
the groups.

Is there a limit to the number of databases you can attach to one workgroup
file? If so, can you tell me what that limit is? If no limit exists, is
there any disadvantage to continuing to use one workgroup?

 

[Rick Brandt]

I have several databases attached to the same workgroup file. This makes
it easier for the users to remember only one password for several
databases and also makes setting security easier for me because I set
permissions using the groups contained in the workgroup file and the users
are already assigned to the groups.

Is there a limit to the number of databases you can attach to one
workgroup
file? If so, can you tell me what that limit is? If no limit exists, is
there any disadvantage to continuing to use one workgroup?

MDB/MDE files are not attached, linked, or referenced in any way to
workgroup files. The way secured Access apps behave gives the superficial
appearance that there is a connection of some kind, but there actually is
not.

What actually happens is that a workgroup is used for any given Access
session and then that session opens (or attempts to open) Access files.
Information in the workgroup file is used to allow or deny the session from
opening the Access file. For a secured file this information just happens
to only exist in certain workgroup files whereas for unsecured files any old
workgroup will suffice.

Given the above description it should be apparent that a workgroup file can
be used to open an unlimited number of Access files.

 

[AccessIM]

Thanks for clarifying that, Rick.

MDB/MDE files are not attached, linked, or referenced in any way to
workgroup files. The way secured Access apps behave gives the superficial
appearance that there is a connection of some kind, but there actually is
not.

What actually happens is that a workgroup is used for any given Access
session and then that session opens (or attempts to open) Access files.
Information in the workgroup file is used to allow or deny the session from
opening the Access file. For a secured file this information just happens
to only exist in certain workgroup files whereas for unsecured files any old
workgroup will suffice.

Given the above description it should be apparent that a workgroup file can
be used to open an unlimited number of Access files.



.