Re: Basing Object Permissions on Ownership

Tech-Archive recommends: Fix windows errors by optimizing your registry


> I'm creating a database where I'd like to prevent users from making any
> design changes, etc. to objects that I've created but at the same time I
> want them to be able to create their own objects. One problem I'm trying
to
> overcome is how to handle situations where I want to be able to send them
> new objects I've created without them inheriting all of the permissions
I've
> assigned to New Objects. Is there a way of assigning permissions to
> individual objects based on ownership of the object through VBA or some
> other method? Hopefully what I'm trying to do is clear. I should also
point
> out that the security is working on the objects I've created in the past
so
> that is not an issue.

I believe that a user can create their own objects regardless of what
permissions they have on new objects. If your user creates a new object then
they will be the owner of that object and they will be able to do whatever
they want to do with that object. As long as they don't have modify design
permissions on new objects then they won't be able to change the design of
objects which you create and add to the database (or objects created by
anyone else for that matter) but they will still be able to create their own
objects.

For example, if a user has read design permissions on new queries but does
not have modify design permissions then they would be able to open and view
a query which you created but they wouldn't be able to modify the design of
the query or to delete the query. They would, however, be able to create
their own queries and do whatever they want to those queries because they
would be the owner of those queries which would give them inherent
permissions to those queries.

I'm not suggesting that it's a good idea to let users create their own
objects but if you have no choice, this would do what you want.


>
> I trust one of you gurus out there has dealt with such a situation and can
> enlighten me on the best way to handle it.
>
> Thanks.
>
> Brian
>
>


.

Relevant Pages

  • Re: URGENT HELP PLEASE - stopping someone importing my queries
    ... it does not prevent a Query design being read. ... > If your queries contain design secrets, you may be able to partially hide what ... > permissions, called something else of course, and join them to that. ... >> new database, copy my original using File Import and then has access to my ...
    (microsoft.public.access.devtoolkits)
  • Re: Protecting Database frm being Imported into a new Database
    ... The permissions that you set on forms, reports, etc in an MDB file can ... users can see the design of the ... However, users can create a new database, import an object, and play ...
    (microsoft.public.access.security)
  • Re: How to copy ACLs from one OU to another?
    ... On the design question... ... have an OU for each remote office (City), and under the City OU are 3 OUs, ... have to recreate all those custom permissions for the User/Group/Computer OUs ... > directory to take use of inheritance I strongly recommend that. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Read design/read data problem
    ... An alternative is to deny all permissions on the tables, ... They won't be able to open tables directly, nor read their design. ... Create a startup form that is opened on ... If you need to bypass these startup features, you can hold the shift key ...
    (microsoft.public.access.security)
  • Re: Basing Object Permissions on Ownership
    ... >> design changes, etc. to objects that I've created but at the same time I ... Is there a way of assigning permissions to ... if a user has read design permissions on new queries but does ...
    (microsoft.public.access.security)