G
Guest
We all know that Access mdb apps bloat with use and must be compacted
periodically. I think I read somewhere why this happens but I can't recall.
On an app I am working on, I noticed I was up around 50MB and compacted
before I had to send to another developer by email. Compacting reduced it to
about 10MB(zips to about 3MB). For some reason, I decided to create a new
database and import all the objects from the app. The size of the resulting
database is only about 5MB, which after zipping to about 1MB (which made the
other developer happy, as he only has dial-up connection, and smaller emails
are better).
I was curious if anyone knows why compact method doesn't reduce the size to
something similar to that when all the objects are just imported into a new
database?
periodically. I think I read somewhere why this happens but I can't recall.
On an app I am working on, I noticed I was up around 50MB and compacted
before I had to send to another developer by email. Compacting reduced it to
about 10MB(zips to about 3MB). For some reason, I decided to create a new
database and import all the objects from the app. The size of the resulting
database is only about 5MB, which after zipping to about 1MB (which made the
other developer happy, as he only has dial-up connection, and smaller emails
are better).
I was curious if anyone knows why compact method doesn't reduce the size to
something similar to that when all the objects are just imported into a new
database?