Strange Compact and Repair Database Behaviour

[bejhan]

I am using MS Access 2003. I have a database I have been developing for about
2 months. Everytime I used compact and repair I had thought it was working
but apparently not. What happens is the status bar says compacting and it
finishes the processes then reopens my database.

The problem is that the process has left behind db1.mdb and not compacted my
database at all. When I go into db1.mdb it has all of my forms, modules, etc.
and seems to be working. I don't want to make this assumption in case I am
wrong. My database is around 43MB with no data in the tables. db1.mdb becomes
around 3MB.

Why is this happening and how can I fix it? I have tried importing all of
the items from the database into another (once complete this is only around
3MB) and done a compact and repair with the same result.

 

[tedmi]

C&R works like this: a new dbX.mdb is created and all objects from your mdb
are copied into it. If no problems, your original mdb is deleted and db1.mdb
is renamed to the original. If the deletion fails, you are left with a
compacted db1.mdb and an uncompacted original.

Search this NG for mentions of db1.mdb - there was some discussion of a bug
in A2003 causing this.