Access compression 'db1.mdb' being left behind

[chuggs]

I have a fully patched version of Access 2003 SP3 on an XP Pro machine w/SP2 (also fully patched). Recently, I've begun to notice that when I close my db's (I have 'compress on close' checked in the options), they will compress, but will not delete the db(x).mdb file they leave behind. To my knowledge the databases are not corrupt - they still open and operate w/o a hitch. What is the deal? I've tried doing a compact and repair, using the JET utility from MS, booting in safe mode and removing the .dat files from the temp folder, etc. Any help or advice would be appreciated. It's very annoying. Thanks!

[puppydogbuddy]

I have a fully patched version of Access 2003 SP3 on an XP Pro machine w/SP2 (also fully patched). Recently, I've begun to notice that when I close my db's (I have 'compress on close' checked in the options), they will compress, but will not delete the db(x).mdb file they leave behind. To my knowledge the databases are not corrupt - they still open and operate w/o a hitch. What is the deal? I've tried doing a compact and repair, using the JET utility from MS, booting in safe mode and removing the .dat files from the temp folder, etc. Any help or advice would be appreciated. It's very annoying. Thanks!

One thing that the db1.mdb getting left behind might indicate is that you may not have sufficient available RAM memory and/or insufficient disk space in the directory at the time the compact on close is executed. You can test this by monitoring the available RAM and disk using the free System Internals software at the following link:

http://www.microsoft.com/technet/sys...s/default.mspx

[ajmuller]

s. http://access.softwareheadlines.com/...ss-t54583.html

Regards Andreas

[puppydogbuddy]

s. http://access.softwareheadlines.com/...ss-t54583.html

Regards Andreas

Andreas,
Thanks very much for sharing this information. This is the first I have heard of Access requiring full permissions for the database to execute a clean compact on close.

PDB