Changing Ownership of a Database

[LittleSmudge]

As part of the security setup of some databases I have been changing the OWNERSHIP of the various database objects. ( Via the Tools, Security, User & Group Permissions, Change Owner tab )

I can happily change ownership of Forms, Reports, Queries, Tables etc - but I can't change the Ownership of the Database object itself.

Some Dbs have the Owner "Admin" and some have the owner as a Custom User.
Even if I log on as that User ( Who is a member of the "Administrators" group which has 'All Powers' ) the Change Owner button is grayed out.


What do I have to do to set the Owner of the Database ?




G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.

 

[Bob44TheCat]

Hi,

You can't actually change the ownership of a Database, as the database owner is the userid that was in effect when the database was created. To get round this, you need to create a new, blank database whilst logged in under the userid of your custom user (i.e. the user you want to be the database owner), and then import all objects from your existing database. Your new database is then your production version.
Two points - 1. This pre-supposes that you have (or will have) all other aspects of database security in place, i.e. dedicated workgroup file, all permissions removed from user 'Admin' and groups 'Users' and 'Admins', etc.
2. You will need to ensure that users actually log on to the new database (which will have a different name to the current one) - if they have shortcuts set up on their desktops to open the database, change the target file name.
Hope this helps,
Cheers,
Bob.

 

[LittleSmudge]

Thanks Bob.

Now I understand.

and as for your points
1) - oh Yes - ALWAYS

2) With Admin having no rights at all they always have to log in via a shortcut icon.
But surely if I rename the old file and make the newfile the name that they all know then there will be no need to change the users' icons.




G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.

 

[Bob44TheCat]

Hi again,

Yep, I think renaming should work OK - but as with everything else in Access, backup first and test thoroughly afterwards (I know I'm preaching to the converted, but it never hurts to say it again ).
Cheers,

Bob.