views:

479

answers:

2

A client is receiving a "You don't have permission to read [REPORT NAME]" error message when attempting to launch a report in a MS Access database. When I go to the “Change Owner” tab under Tools > Security > User Groups and Permissions, the owner is <unknown>. If I attempt to change the owner, I get a "You don't have permission to change the owner of [REPORT NAME]." error message.

How do I reclaim the object so I can restore its permissions?

A: 

Can you assign "Open/Run" permissions to the report? Ordinarily, you shouldn't have to change the owner to allow a user group (or individual user accounts) Open/Run permission. However, I don't know if it will operate differently when the current report owner is unknown to Access ... I've never encountered that situation.

Will it let you re-assign the report owner when you log into the database with an account which is a member of the Admins group?

HansUp
The database isn't really using any of the security configuration (no login required), so it should be the "default" setup. The dialog is showing "Admin" next to Current User. I tried just granting Open/Run permission and got the same permission error.
Andrew Dyer
In that case, the only thing I can suggest is to try importing your database objects into a new blank database. However, I'm skeptical about whether it will resolve the problem. I'm stumped.
HansUp
Objects that can't be read won't be readable through an import. He needs to find the original workgroup file and open Access with it in order to get access to the objects. He can then assign full permissions to the default Admins group and then it will work with the default workgroup file.
David-W-Fenton
A: 

I ended up finding a copy of the database from a month ago and importing the inaccessible reports into a blank Access database file. Then, I imported the remaining database objects from the current copy of the database. Problem solved.

As far as I know, they have never used MS Access/MDW security on the database, so I suspect it's just a symptom of an old Access database that's ripe for a .NET/SQL Server migration.

Andrew Dyer