I have been experiencing several issues related to Compact and Repair on my database.
The original file is 125MB and I deleted some obsolete records (not many though) and several unused tables, forms, and reports trying to get the db back down to a more manageable size for off-site users.
After making these changes, I compact and repair, the new database file is actually LARGER (by 3 MB or so) than the original AND three new files show up in the directory: "db_backup.mdb" and "db1.mdb" and "db2".mdb that were NOT there prior to the compacting. The "db_backup" file is identical in size to the new file (after compacting); however the other two db files are less than half the size. I can open them and they seem to act/appear the same as the original/compacted version, as does the backup one. There are no "Paste Errors" or other newly added tables in any of the versions either.
Does anyone have any idea why all of this is going on???
By the way, I just tried compact/repair on another database in a different directory (though both locations are still on a network server) and I get the "db1.mdb" file created that is quite a bit smaller in size, but appears identical when opened. There is no "_backup.mdb" created though.
Some more insight...When I copy the database to a local folder and then run the compact/repair, none of this happens and the file compacts down to a reasonable 58MB (the same size as the db1/db2 files that were created on the network location). Now this database has been living on the network for several years and I have only recently started having this problem...
Thanks again!
The original file is 125MB and I deleted some obsolete records (not many though) and several unused tables, forms, and reports trying to get the db back down to a more manageable size for off-site users.
After making these changes, I compact and repair, the new database file is actually LARGER (by 3 MB or so) than the original AND three new files show up in the directory: "db_backup.mdb" and "db1.mdb" and "db2".mdb that were NOT there prior to the compacting. The "db_backup" file is identical in size to the new file (after compacting); however the other two db files are less than half the size. I can open them and they seem to act/appear the same as the original/compacted version, as does the backup one. There are no "Paste Errors" or other newly added tables in any of the versions either.
Does anyone have any idea why all of this is going on???
By the way, I just tried compact/repair on another database in a different directory (though both locations are still on a network server) and I get the "db1.mdb" file created that is quite a bit smaller in size, but appears identical when opened. There is no "_backup.mdb" created though.
Some more insight...When I copy the database to a local folder and then run the compact/repair, none of this happens and the file compacts down to a reasonable 58MB (the same size as the db1/db2 files that were created on the network location). Now this database has been living on the network for several years and I have only recently started having this problem...
Thanks again!
Last edited:
