Permissions for mSysTables object

[Silvester]

Hi,

I recently secured my app fe, revoking default admin user privileges on most
objects to open/read and sending default admin to the users group. I have
also revoked appropriate permissions on the users group.

I distribute the app without the workgroup file.

Users have been getting the error "You do not have the permissions to use
the MsysTables object"

What permissions do I need to grant to avoid this error ?

 

[Scott McDaniel]

If you allowed Admin permissions on the Users group, then your app is, for
all intents and purposes, not secured as ALL users are members of the Users
group and cannot be removed from same. Also, if you didn't distribute the
..mdw file with your database, then your users should not be able to even
open the database ... assuming the db was properly secured, which apparently
is not the case here. I would urge you to download and read-read-read the MS
Access Security FAQ, follow the steps diligently, and begin your
understanding of Access security. It is complex, and purposely so. When
securing your database, you should open a new, blank db WITH the custom
workgroup you created for you app and import all objects ... this will
likely take care of the issue you have with the MSysTables object.

 

[Joan Wild]

Are you changing the SQL for saved queries in code? If so, you need to give
users permission to modify design on those queries.

 

[Joan Wild]

Actually Scott, providing Silvester did it properly, there is nothing wrong
with securing a mdb, setting permissions on the built-in accounts, and not
shipping the mdw you secured with.

It is perfectly valid, and useful if you don't want users to have to log in,
and you only need one level (group) of permissions.

 

[Silvester]

Thanks Scott & Joan,

I knew I was doing something right. I did follow the SECFAQs and wound up
with the msystables error.

Yes, Joan, I am changing the SQL in queries and thats probably it. I will
grant mod permission for users and try again.

 

[Silvester]

You were right, Joan. Once I granted mod permissions to users on my query in
which the sql was being changed on the fly using code, all errors stopped.

Thanks for the help.

 

[TC]

It seems a weird error message for that situation. You'd think it should say
"no permission to modify query BLAH", or somesuch.

TC