Seems like bad security practice to have the client application protect the source data. A user could create a brand new link to the source database and modify it easily.
Instead, you can make a network drive read-only to some users, and put your HR database there. Or put similar read-only permissions on the HR database accdb file individually within windows file manager. Access can link to tables in a read-only ACCDB file, and it automatically becomes a read-only link in the client database.
Seems like bad security practice to have the client application protect the source data. A user could create a brand new link to the source database and modify it easily.
Instead, you can make a network drive read-only to some users, and put your HR database there. Or put similar read-only permissions on the HR database accdb file individually within windows file manager. Access can link to tables in a read-only ACCDB file, and it automatically becomes a read-only link in the client database.