G
Guest
After Office 2003 SP3 is applied, MS Access 2003 requires Full Control
permissions to properly compact a database. This means changing permissions
all over my network shares from "Modify" to "Full Control". Tech Support
says that this is a "Security Enhancement" in Access 2003 SP3 and the only
work around at present is to ask users to copy DB1.mdb back over the original
mdb, or to set "Full Control" permissions on every share where Access DBs are
stored.. I feel is it a "Security Threat" to have to allow all my users to
be able to change permissions. I would like to see Microsoft fix this
"Security Enhancement" as soon as possible.
Symptoms: Access 2003 "Compact and Repair" fails to overwrite the original
mdb file and leaves a new dbX.mdb file each time it compacts. This caused
our file shares to grow very rapidly, as we have a large number of large DBs
that have "Compact on Close" checked. We found db1 - db14.mdb were created
for many databases.
Any chances of a quick hot fix to remedy this?
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...0fb3e351b&dg=microsoft.public.access.security
permissions to properly compact a database. This means changing permissions
all over my network shares from "Modify" to "Full Control". Tech Support
says that this is a "Security Enhancement" in Access 2003 SP3 and the only
work around at present is to ask users to copy DB1.mdb back over the original
mdb, or to set "Full Control" permissions on every share where Access DBs are
stored.. I feel is it a "Security Threat" to have to allow all my users to
be able to change permissions. I would like to see Microsoft fix this
"Security Enhancement" as soon as possible.
Symptoms: Access 2003 "Compact and Repair" fails to overwrite the original
mdb file and leaves a new dbX.mdb file each time it compacts. This caused
our file shares to grow very rapidly, as we have a large number of large DBs
that have "Compact on Close" checked. We found db1 - db14.mdb were created
for many databases.
Any chances of a quick hot fix to remedy this?
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...0fb3e351b&dg=microsoft.public.access.security