biggail
Head Administrator
Global user
Registered: 03-2005
Posts: 13
Karma: 0 (+0/-0)
|
|
Reply | Quote
|
|
Access doesn't delete DB1 file after compaction
This is a well-documented problem which still bedevils users. It seems to only be a problem on Windows 2003 installations with Access 2003. There is a hotfix on the Microsoft website:
http://support.microsoft.com/kb/945674
This is a description of the problem that is fixed, hopefully, by the hotfix or by giving users full control of the folder:
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.
|
|
10/17/2008, 11:39 am
|
Send Email to biggail
Send PM to biggail
Blog
|
