By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,859 Members | 1,351 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,859 IT Pros & Developers. It's quick & easy.

Microsoft access cannot delete the original mdb file after compacting it.

P: 18
Hi all,

The following problem is occuring for a particular user who doesn't have full permissions to the shared folder.

[IMG]Microsoft Office Access cann't delete the original mdb file after compacting it.The compacted one is named with some other name and stored in the folder.
The original database was not deleted because it is read only.[/IMG]

How to resolve this issue.Is there any solution other than giving full permissions to the user?
Sep 23 '08 #1
Share this Question
Share on Google+
2 Replies

Expert Mod 2.5K+
P: 2,545
Hi. I guess you have Compact on Close set on; there are two reasons why you should turn it off. The first (and most important) is that Compact on Close can introduce errors in Access databases running across a network if something happens during the compact process, leading to database corruption.

The second is that because the compact process creates a new database and deletes the old one your users must have create and delete rights to the network directory concerned if you want them to have the right to compact the database.

In general there is no need to use Compact on Close with Access. Compacting the database file as it grows can be done by whoever administers the database as needed (depending on how quickly the database file grows in use) - say weekly or monthly at most. As always, a full backup should be taken first.

Sep 23 '08 #2

Expert 2.5K+
P: 3,532
Everything Stewart says is right on the money, of course, especially that last line! A backup should always be made before compacting the database, because of the possibility of corruption! Compact on Close is possibly the most dangerous feature Microsoft has ever added to Access, because of this.

After reading this thread, another question comes to me. When you say that this mdb is in a shared folder, is this referring to a back end in a split database? If this is referring to an un-split database being shared by multiple users thru a shared folder, you are once again courting disaster. All multi-user Access databases should be split into front end/back end with a copy of the front end residing on each user's PC and the back end only, with the tables, being on a shared folder.

Welcome to Bytes!

Linq ;0)>
Sep 23 '08 #3

Post your reply

Sign in to post your reply or Sign up for a free account.