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

Compact on close

P: 2
Using Access 2003
This applies to db's with the Compact On Close option set to yes. Recently and randomly db#.mdb started showing up. The source db did not compact but is not damaged. I am at a loss as to what is gong on here.
Thx for any insight.
Jan 10 '08 #1
Share this Question
Share on Google+
3 Replies

P: 45
During the Compact on Close a new database is created (db#) all the original objects are cloned clean and then moved to the db# file. The original database is then deleted and the new one renamed to the original name. If you ended up with the db# file then it never finished the Compacting process. Either due to errors in your database or a comm error. Database errors during compacting are very common in multi-user setups where the forms are being shared.
Jan 10 '08 #2

P: 2
Most of these db's are just report generators - the only interaction is thru an automated scheduler - the db#.mdb is a compacted copy of the source. Any suggestions as to how I check a comm problem? I gone thru teh event logs with no success.
Jan 10 '08 #3

P: 45
Well if the db# is a fully functional db then I would look at the security rights of the folder where the database resides. It appears you have made it through the entire Compact process except for the delete and rename. So I'm betting you don't have delete rights to the original or for some other reason it can't be deleted (user or server lock).
Jan 10 '08 #4

Post your reply

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