Compact and Repair - creates new file

  • Thread starter Thread starter Jeff C
  • Start date Start date
J

Jeff C

Using Access 2003 in XP Pro - recently a new file "db1.mdb" is created
during each compact and repair of any database I have. It is basically a
copy of the database being compacted.

Did I miss reading about an issue out there or could someone tell me how to
resolve this?

Thanks in advance.
 
If you compact into the same database file, that won't happen. You may have
a permissions problem causing this, or there may be a slight corruption in
your database which causes the operation to truncate before completion.
 
--
Jeff C
Live Well .. Be Happy In All You Do


Arvin Meyer said:
If you compact into the same database file, that won't happen. You may have
a permissions problem causing this, or there may be a slight corruption in
your database which causes the operation to truncate before completion.
Click to expand...

I am not doing anything consciously different and this is happening to every
database I use, probably 20-30 of them. Is there a pointer that allows the
database to compact into a different database?

Thanks
 
Using Access 2003 in XP Pro - recently a new file "db1.mdb" is created
during each compact and repair of any database I have. It is basically a
copy of the database being compacted.

Did I miss reading about an issue out there or could someone tell me how to
resolve this?

Thanks in advance.
Click to expand...

The way Compact works is to create a new db1.mdb; copy everything from the
current database into it; delete the current database; and rename db1 to the
old name. If any step in this chain fails you'll get the db1 left hanging
around.

Open db1.mdb and see if there is a CompactErrors table. If so, read its
contents - it should give a hint as to the problem.

Alternatively, you might not have sufficient Windows privileges to rename or
delete a file in the folder containing the database.
 
I've had this happen if someone else has the database open when I try to
compact it.

Mikearelli
 
David said:
What John W. Vinson says is correct. If still you face the same problem than
there may be a slight corruption in your database which causes the operation
to truncate before completion. For that you need third party tool to repair
your mdb file. Try
http://www.repair-access-file.com/download-access-file-recovery.php
Click to expand...

Ah, yet another posting by an employee of that company.

For more information on corruption including possible causes,
determining the offending PC, retrieving your data, links, official MS
KB articles and a list of vendors who state they can fix corruption
see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a free, convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
 
Be aware that this is commercial software and Wangdong is posting from the
datanumen.net.

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
 
Back
Top