Re: Becoming the Owner

Sprinks wrote:
For some reason, I am not the Owner of my back-end database, which prevents
me from setting any permissions regarding new objects.

The owner isn't the only user who can set permissions on objects. You just
need to log into the database as a member of the Admins group to set
permissions. But your description prompts a question.

When you check the current owner of <Current Database>, does it say <Unknown>,
or does it say another user's name? If it's <Unknown>, then that means
you've logged into a database that was created using a different workgroup
file, but it wasn't secured properly (which is very common). If it were
secured properly, then you wouldn't have been able to open it while joined to
a different workgroup. If another user's name is listed as the owner, then
you just need to log into the database as that user to have the owner's
privileges again.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200609/1

.

Relevant Pages

  • Re: Microsoft has utterly failed with Access 2007
    ... Any idea why MS did away with user-level permissions? ... our database from Access 2003. ... Before we set up a workgroup with user-level ... Access 2007 has no way to set permissions at the user and object level. ...
    (microsoft.public.access.modulesdaovba)
  • Re: security for 100+ user and dbs without having to signin
    ... The owner of a DB can always give themselves permissions. ... by someone unaware of security, then likely they were logged in as ... > database remove all unnecessary permissions from ...
    (microsoft.public.access.security)
  • Re: Viewing object owner in SQL 2005 - ownership chaining
    ... The server principal "HFDB_2_0_readonly" is not able to access the database "Hotfix_data" under the current security context. ... To add on to Erland's response, the user needs a security context in both databases, even if no permissions are granted. ... I'm trying to set up Ownership Chaining. ... When I set up both a table and view from one logon and granted permissions to the view it didn't work, evidently because "creating user" is not equivalent to OWNER. ...
    (microsoft.public.sqlserver.security)
  • RE: Access 97 Security issue Cant make a MDE
    ... "If the database is secured using user-level security, ... logged in as the owner of the database, or at least a member of the Admins ... > the dayabase as a user AND can sign in simply as admin, ... > that the user account has Modify Design or Administer permissions for the ...
    (microsoft.public.access.security)
  • Re: Problem with database
    ... Perhaps running the security wizard. ... report that there is no permissions to read or write them. ... tables with the problem report the owner as unknown. ... For background info the database is normally Access97 but the user has ...
    (microsoft.public.access.security)