MSysTable Permission....

[jsader98]

The programmer who built this access program is no longer here...Everytime I create a new Report, it works great for me...but the person I made it for ALWAYS gets the MSystable permission error....I have gone through the wizard to give them every permission available on the report and the query it is using...AND went and made sure permission was given on the SQL side of things as well...YET I still get this incredibly annoying error...that seems there is no real answer to...CAN ANYONE help?!!! even compacted and repaired the program...still no good....I know it will be something small, but I can not see it.

 

[nateobot]

I 'think' you can go to Tools | Options. Look on the Tables/Queries tab and choose Owners for the Run Permissions. (Access2k)

 

[jsader98]

Thanks for the tip...but the owner is what it is suppose to be...and works for all the other queries. I wish it had been that easy...thanks for the help though...if you come across anything else let me know please....

 

[The_Doc_Man]

MSysTable is one of those "special" tables that is normally not visible when you open the tables panel of the DB window. You have to go to the Tools and drill down to where for tables you can see "Hidden" and "System" tables. When you do that, you can then use tools to get to the permissions of the MSysTable table and see if it has some sort of permission denial.

Another possibility exists, though. If this is a split DB (FE, BE separate), it is possible that one of the two MSysTables has different permissions from the other. A third possibility is that the permissions in the workgroup file are hosed up. See, the workgroup file is just another Access DB with a set of special tables it in. But I believe it also has an MSysTable table that can have permissions on it that would deny certain access rights.

I don't know if this will help you or not, but it might give you a couple of other places to look.

 

[jsader98]

Thanks Doc,
I will see if I can drill into those tables...Did learn one interesting fact....We have a server here locally running SQL then two servers over seas running SQL (don't ask...) Anyhow...the person that is having permission problems was trying to hit our local server and it was throwing that error...when they change the ODBC to hit the drivers overseas....it works just fine...EVERYTHING is the exact same with the exception that we hit the server over seas....I just don't get it at this point. Any help would be greatly appreciated...

 

[The_Doc_Man]

jsader98, you have a starting point. You have a place that works and a place that doesn't. Time to start finding differences. And trust me, those differences DO exist. But your reply throws me for a loop here. If you have ODBC and three servers running SQL (I'm assuming SQL Server), I didn't know SQL Server had an MSysTable. If it behaves like Access, though, it has a security list - perhaps an Access Control List - and somewhere, you have an issue with one of the permissions.

Do you know if SQL Server "officially" recognizes Windows intrinisic groups like "CreatorOwner" "Everyone" "Interactive" "Authenticated Users" "Operators" and other pre-defined Windows groups? If so, don't rule out permissions relating to Windows groups as well as the ones defined for your app.