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

Database1.mdb does not delete after compact

P: n/a
I've got several Access 2000 databases that are currently being run
with Access 2007.

When the databases close, I've got them set to compact on close. This
creates the database1.mdb file, however once the database has finished
compacting and the database is closed, the database1.mdb still remains
in the folder. As a result, the next time the database closes, it
creates a database2, which it does not delete, and this continues each
time the database is closed.

This appears to ponly be happening on the databases that I have up on
my company's network, but does not happen on the databases I have on
my local C:\ drive.

Does anyone know why this would happen, and how to fix it?
Aug 6 '08 #1
Share this Question
Share on Google+
2 Replies


P: n/a
I am experiencing the exact same problem and would love to hear the
solution to this...

J. D.

Aug 6 '08 #2

P: n/a
JvC
My guess is you don't have delete rights on the network drive. When you
do the compact, you have to delete the original mdb and then rename the
database1.mdb version. Check with your network admin, and they should
be able to sort it out.

A second possibility, and an ugly one, is that you have multiple users
opening the database on the network. In that case, user 2 can't delete
the database because someone else has it opened, and the numbered
versions hang around.

Good luck!

John

Icarus formulated the question :
I've got several Access 2000 databases that are currently being run
with Access 2007.

When the databases close, I've got them set to compact on close. This
creates the database1.mdb file, however once the database has finished
compacting and the database is closed, the database1.mdb still remains
in the folder. As a result, the next time the database closes, it
creates a database2, which it does not delete, and this continues each
time the database is closed.

This appears to ponly be happening on the databases that I have up on
my company's network, but does not happen on the databases I have on
my local C:\ drive.

Does anyone know why this would happen, and how to fix it?

Aug 6 '08 #3

This discussion thread is closed

Replies have been disabled for this discussion.