Forum Discussion
Security Conflict
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 a...
- 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.
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.
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.
Thank you Tom. Obviously not the answer I was hoping for but we'll get passed it.
