Question Strange things happening when compacting

[branston]

Hi. I have a front end of a database which was around 21,000 KB. I did a compact and repair, and the size went up to 25,000. However, there is a new file called db1 which is 8,000 (The size i would expect my main file to be after the compact).
It almost seems like its getting 1/2 way through the process, but not deleting the temporary file it creates.
If i open db1 it SEEMS to be a fully functioning copy of the original.
Any ideas whats going on here?!
Thank you!

 

[namliam]

A compact is basicaly this:
- Make a new (blank) database called DB1
- Copy all objects in the existing Current DB to DB1
- Delete the current DB
- Rename DB1 to Current DB

Obviously your finding is right... DB1 is the correct/compacted version, for some reason the delete of the current db failed causing the compact to fail.

 

[MStef]

I think it's hapened because you did not open your FE as "exclusive", and somebody (another user) start the application before the compacting finished.
Open your FE as "exclusive", and make a compacting again.

 

[branston]

Thanks for your confirmation/suggestions.
MStef, I thought the same thing, but the FE I was compacting is a personal file - Only I have access to it. Could there be any other reason?
Thanks!

 

[David Eagar]

Import all objects into a new database, then compact & repair. Don't know the cause of the problem, but I have have had this before and this is a solution

 

[branston]

Great, thanks for that David.

 

[boblarson]

One other thing that can cause the db1 to remain is that you don't have delete permissions on that folder where the database is located. Now, if it is on your personal machine, that isn't likely. But, if on a network drive, it could very well be possible that you haven't been given delete permissions, where you would need them.

 

[WayneRyan]

Fortunately I haven't had to deal with this issue for quite a while, but I
remember some things about it.

There is probably a corrupted Form or Table in your database.

Access gives up on the process when it is encountered. The DB1.mdb
file *might* be valid, but I wouldn't count on it.

You could try starting the DB with the /Decompile switch, then retry
the compact/repair.

If you try to import ALL objects into a new, blank database that might
fail when Access encounters the corrupted object. If it doesn't fail
then you're good to go.

You might try importing all tables first, then forms, etc. That should narrow
down the list of suspects.

Wayne

 

[branston]

Thanks for all your suggestions.

I copied all the information into a new database, and it seems to work now. If I have the problem again then I will try and find if there is anything corrupted.

Thanks again for all your help.