SOLVED

Security Conflict

Copper Contributor

Good day,

We are using MS Access 2016 (and Office 365) in conjunction with a 20 year old MDB database that was not converted to an .accdb database.  It has been working fine until a couple of days ago.  The Db is divided into small, similar front-end Dbs and a much larger back-end Db on a shared network drive.  On 4 of 5 workstations where the front-ends are installed we have no problems to speak of.  On one workstation VBA is giving me grieve.  It looks like a library is lost as VBA code no longer runs properly.  Obviously to change anything and save the changes in the front-end Db, I need exclusive access.  I cannot solve the dilemma of granting the "admin" ( = only user) exclusive access.  The admin logically has "administer" access.  When I try to set the flag for "open exclusive" I get the following message: You cannot change permissions for "Current Database". To change permissions for this object you must have Administer permissions for this object.
This very much feels like a conflict as I do have Administer permissions.
Looking forward to any good advise.  Thank you.

IMG-20240612-WA0001.jpg

2 Replies
best response confirmed by EricJ_Canada (Copper Contributor)
Solution
You're getting that error because you are not logged into Access as a user with full permissions, using the special workgroup file (*.mdw) that specifies the users and permissions.
You will need to locate the correct MDW file, and use it in a command line for msaccess.exe with the /wrkgrp command line switch (there are other ways, but this is easiest).

If you want to "change anything", you should first download, study, and fully understand the Access Security FAQ from MSFT. I hope you can still find you, because you are in real dinosaur territory.
My best advice is to abandon this "workgroup security" altogether. MSFT realized 17 years ago it was not worth keeping - too complicated for most users. You should get with the program and upgrade, and implement security a different way.

@Tom_van_Stiphout 

Thank you Tom.  Obviously not the answer I was hoping for but we'll get passed it.

1 best response

Accepted Solutions
best response confirmed by EricJ_Canada (Copper Contributor)
Solution
You're getting that error because you are not logged into Access as a user with full permissions, using the special workgroup file (*.mdw) that specifies the users and permissions.
You will need to locate the correct MDW file, and use it in a command line for msaccess.exe with the /wrkgrp command line switch (there are other ways, but this is easiest).

If you want to "change anything", you should first download, study, and fully understand the Access Security FAQ from MSFT. I hope you can still find you, because you are in real dinosaur territory.
My best advice is to abandon this "workgroup security" altogether. MSFT realized 17 years ago it was not worth keeping - too complicated for most users. You should get with the program and upgrade, and implement security a different way.

View solution in original post