Changing ownership/permissions on Data .mdb file.

[Marvinator]

I'm working on securing a database, and while working on changing
ownership of the objects in the database, the book in which I'm working
has the following "Tip"
<i>Changing the ownership of tables in the application .mdb file only
changes ownership of the links to the back-end tables ijn the data .mdb
file. You must also change ownership of (and set appropriate
permissions for) the data .mdb file.</i.

I can't find any information further on this in this book as it moves
on to other areas of permissions, so I'm a bit confused at this point.

Can someone point me in the right direction here?

 

[Keith Wilby]

I'm working on securing a database, and while working on changing
ownership of the objects in the database, the book in which I'm working
has the following "Tip"
<i>Changing the ownership of tables in the application .mdb file only
changes ownership of the links to the back-end tables ijn the data .mdb
file. You must also change ownership of (and set appropriate
permissions for) the data .mdb file.</i.

I can't find any information further on this in this book as it moves
on to other areas of permissions, so I'm a bit confused at this point.

Can someone point me in the right direction here?

The tip assumes that you have a database split into front and back ends. In
the back end you would have your tables and in the front end you would have
linked tables (linked to the BE). Search the help for "split database".

Keith.
www.keithwilby.com

 

[Joan Wild]

I'm working on securing a database, and while working on changing
ownership of the objects in the database,

This sounds (maybe) like you are using the Change Ownership feature of the
security dialogs. If so, you should understand that you cannot change the
owner of the database object, which is one of the most important ones to
change.

I can't find any information further on this in this book as it moves
on to other areas of permissions, so I'm a bit confused at this point.

Can someone point me in the right direction here?

If your database is split, you have to secure both the frontend and the
backend. You'd join your secure workgroup file and then proceed to secure
the backend mdb - i.e. create a new mdb and import the objects, and then set
permissions...