mdw security file

[mar10]

I have 2 questions regarding Access security.

I have a database that users are activating via a desktop icon that
includes a reference to the .MDW file. The individual that asked me to
help set this up just wants to keep inexperience users from
accidentally removing data; they really don't have huge security
issues. Some individuals are still opening the database directly
from access bypassing this .MDW file activated via the icon. Are
there any problems that I'm not thinking of in having individuals
open the files via 2 different methods? The individuals using the
direct Access program are all experiences and have free reign over the
program/data. Just want to make sure we haven't overlooked any
issues that may crop up that would cause problems with the database
function.

Second question, when I sent up a new group and am giving that group
permissions can you obtain all the permissions for each item
(table/query etc) quickly by selecting the DATABASE Object Type and
will this trickle down to all the other items, or do I need to select
each Object type individually? Hoping there is a quicker way than
selecting object types one by one when I want to give each object type
the same security level.

Thanks

 

[Rick Brandt]

I have 2 questions regarding Access security.

I have a database that users are activating via a desktop icon that
includes a reference to the .MDW file. The individual that asked me
to help set this up just wants to keep inexperience users from
accidentally removing data; they really don't have huge security
issues. Some individuals are still opening the database directly
from access bypassing this .MDW file activated via the icon. Are
there any problems that I'm not thinking of in having individuals
open the files via 2 different methods? [snip]

The fact that the file CAN be opened without the proper MDW means that it is not
secured properly. Other than that it makes no difference.

Second question, when I sent up a new group and am giving that group
permissions can you obtain all the permissions for each item
(table/query etc) quickly by selecting the DATABASE Object Type and
will this trickle down to all the other items, or do I need to select
each Object type individually?

Individually, but until you fix your incorrect security it won't make much
difference anyway.

 

[david epsom dot com dot au]

I have 2 questions regarding Access security.

I have a database that users are activating via a desktop icon that
includes a reference to the .MDW file. The individual that asked me to
help set this up just wants to keep inexperience users from
accidentally removing data; they really don't have huge security
issues. Some individuals are still opening the database directly
from access bypassing this .MDW file activated via the icon. Are
there any problems that I'm not thinking of in having individuals
open the files via 2 different methods? The individuals using the
direct Access program are all experiences and have free reign over the
program/data. Just want to make sure we haven't overlooked any
issues that may crop up that would cause problems with the database
function.

No problems. The fact that they are using different databases
(mdw) for there security lookups is no more different than
using different databases for anything else.

Of course normally we try to set up security so that
user have to look in the same database for security
settings, or at least in a copy of the same database.

If anything, we would normally set it so that the naive
user could use any security database for security lookups,
and the experienced users would have to use a particular
security database (mdw) for security lookups if they
wanted to do advanced deletions and changes.

Second question, when I sent up a new group and am giving that group
permissions can you obtain all the permissions for each item
(table/query etc) quickly by selecting the DATABASE Object Type and
will this trickle down to all the other items, or do I need to select
each Object type individually? Hoping there is a quicker way than
selecting object types one by one when I want to give each object type
the same security level.

Thanks

No. If you want that, look around for some sample security
scripting code.

By the way, be aware that Database admin permission is
NOT security admin permission. The Database admin property
is different from the Table/Query admin property.
Database admin permission controls database properties
typically set by an administrator. Security admin
for the database is controlled by the security
Admins Group, not by the Database Admin permission.

(david)