Just wondering if anyone has run into this.
I have a backup/compact procedure similar to Roger's example here
The code copies the original then invokes:
DBEngine.CompactDatabase sOriginalBackup, sCompactedBackup
The problem is that it really isn't compacting the database.
Example:
My original file is 544kb. My backup is 544kb. When I invoke the procedure, the compacted db is only 540kb.
Now, if I run the compact/repair from the tool bar, the DB size is reduced to 476kb.
Has anyone noticed this? Is it normal?
Just wondering aloud.
I have a backup/compact procedure similar to Roger's example here
The code copies the original then invokes:
DBEngine.CompactDatabase sOriginalBackup, sCompactedBackup
The problem is that it really isn't compacting the database.
Example:
My original file is 544kb. My backup is 544kb. When I invoke the procedure, the compacted db is only 540kb.
Now, if I run the compact/repair from the tool bar, the DB size is reduced to 476kb.
Has anyone noticed this? Is it normal?
Just wondering aloud.
Last edited:
