Hi, Ian.

Database files need workgroup files, but they don't really "link" to them.  
Only tables can be linked to.  One my "join" a workgroup to open a particular
database file, because that was the workgroup file used to secure the
database.  This can be done with the Workgroup Administrator, but more
commonly a Windows shortcut is used to open the database file while joined to
the secure workgroup for that particular user session, but the user remains
joined to the default (unsecure) workgroup for all other sessions.  For
example (this is all one line):

"C:\Program Files\Microsoft Office\OFFICE\MSAccess.exe" "C:\Data\MyDB.mdb"
/wrkgrp "C:\Data\Secure.mdw"

In your scenario, I would have one workgroup file with multiple groups --
one for each level of access rights -- and have all the users open the same
front end database file while joined to that workgroup.  However, if you want
to increase maintenance time and effort, you could build multiple front ends
and multiple workgroups.  Each user would use his own shortcut that joins to
the secure workgroup he needs to sign into for his particular level of access
rights and open his appropriate front end.  But that sounds like a lot of
extra work for the developer to maintain this setup.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info.