Compact .mdb not being deleted 3

[rgbanse]

Recently, and randomly, the Db#.mdb files are not being deleted. I am at a total loss.
Any thoughts?
thx
RGB

 

[genomon]

Db1.mdb etc. remaining undeleted indicates that the compact has failed.

Money can't buy happiness -- but somehow it's more comfortable to cry in a Corvette than in a Yugo.

 

[rgbanse]

this is a recent 'happening'
any idea what might have changed to cause this
thx
RGB

 

[genomon]

Usually not enough or fragmented memory. Could also be a fatally corrupted mdb. When was the last time the machine it runs on was defragged?

Money can't buy happiness -- but somehow it's more comfortable to cry in a Corvette than in a Yugo.

 

[genomon]

Forgot one more - has the mdb swollen close to it's max (which I think is 2 gig)?

Money can't buy happiness -- but somehow it's more comfortable to cry in a Corvette than in a Yugo.

 

[rgbanse]

db's are realatively small - not even close to max
started defragging - will let you know if there is improvement
thx
RGB

 

[genomon]

I'm out 'til tomorrow. Worst-case would be creating a new blank mdb & import everything (reset library references if needed).
Good Luck!

Money can't buy happiness -- but somehow it's more comfortable to cry in a Corvette than in a Yugo.

 

[rgbanse]

Defrag made no diff
These are databases that are started by scheduling software. They run a macro that runs reports, then closes db. These db's are all set to compact on close. The original db is still intact, but did not compress.

 

[genomon]

Sorry RGB - outta love here....

Alcohol and calculus don't mix, so don't drink and derive.

 

[JerryKlmns]

What about the permissions on the folder where the compacted mdb is created? Deletion must be allowed!

 

[MTimmer]

Hi,

I have the same problem/error.
Btw, it doesn't only not delete the (temp) db#.mdb file. The compact and repair process isn't completed.
As the process works, it creates a compacted copy of the database as db#.mdb. After which it replaces the original database (Name.mdb) with this compacted version.
It just doesn't do the last part, resulting in an extra file in the folder and a not compacted database.

I've limited the problem to probably the windows (network)security settings. But since no error message is given by either windows or access I can't locate the exact "thing" that causes it.

It's not the folder permissions, because I have all the permissions and I am the owner of the database. (for a short while at least to try to resolve it, not that it helped)
Also, it's not that the database is too large, corrupt, orso. Because the exact same happens when you create an empty (new) .mdb

Now for the funny part.
If you execute the compact process manually using VBA it works like a charm.
You can rename, delete, move, copy, etc via VBA without any problems.

And, for me, the problem only occurs when the database is located on a networkdrive. When I copy the database to the local harddrive the Access Compact & Repair works fine.


I'm not an systemadmin at work, where this problem occurs, so I don't have unlimited possiblities I can try. But the admins at work have been staring at this problem for quite a while now and don't have a lead or solution yet.
And I can't reproduce the problem on my homenetwork.

Think that covers it more or less. I just hope someone has had the same problem and solved it.

 

[MTimmer]

I think I just found what is causing the problem, or at least a possible solution.

I have been browsing the Microsoft support page before, but I guess I have overlooked this:

This article describes the Microsoft Office Access 2003 issues that are fixed in the Access 2003 post-Service Pack 3 hotfix package that is dated December 18, 2007.

This hotfix package fixes the following issues:

....
When you run the Compact and Repair Database utility on an Access 2003 database that is saved on a Windows Server 2003 share, the utility may silently fail. After the Compact and Repair Database utility fails, an additional database file is saved in the same location. For example, if the Compact and Repair Database utility is run on a database that is named Db.mdb, a second database file that is named Db1.mdb is saved.
....

And the link:

http://support.microsoft.com/kb/945674/en-us

I can't check it right now, but I bet this hotfix isn't installed.

 

[thomasks]

Thanks to Mtimmer for the answer!! I was having the same problem with the compact on close not deleting the db#.mdb. After installing the hotfix, problem solved. Great Job!