General discussion

Locked

SMALLER .mdb file size???

By KrizBread ·
I'm using Access 2000 to develop this certain system for more or less 7 months now. Let's call my current system development database as CurrentDB.

I'm just puzzled by this occurrence:

1. I created a new blank database, let's call this new blank database as NewDB.
2. I then imported everything from CurrentDB (my front-end) -- tables, linked tables, forms, reports, macros, modules, including relationships and toolbars.
3. Set-up everything in NewDB to match CurrentDB -- startup, references...
4. Opened the code window and ran Compile to prevent the nasty error of "...connection may have been lost..."
5. Lastly, compacted and repaired the NewDB, then closed it.

To me, both CurrentDB and NewDB are now the same, right? But there's a very large difference in their file size! NewDB is only 7.6MB while CurrentDB is 18.6MB. Note that I've already compacted and repaired CurrentDB prior to comparison.

Could anyone explain this, I mean, how could this be possible? And, is this a safe path to tread whenever I like to have a smaller mdb?

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by CptOmlly In reply to SMALLER .mdb file size???

If you are copying EVERYTHING, why don't you just make copy and paste and rename the .mdb? Seems like a lot of extra work, and greater possibility for error, taking the steps you described. This isn't really an answer, but just an opinion.

I would guess that in the setup of the NewDB, you omitted something by oversight.

Collapse -

by KrizBread In reply to

Thanks for the insight.

But actually, I'm not looking for a means to copy a .mdb file per se =). I was just puzzled why doing what I have enumerated would result to a smaller file.

But during the course of the weekend, I think I came up with an explanation of my own answer. It's in light of Access' DECOMPILE switch. Decompiling a .mdb then compacting and repairing it afterwards causes the "garbage" left behind by the development process (copies-and-pastes, deletions, etc) to be cleared/erased, therefore creating a smaller-sized .mdb.

On the other hand, with the course of action I took as enumerated in my post, NewDB is a fresh .mdb without the garbages present in CurrentDB. Importing everything imports everything but the "garbages" =).

I think this is why =).

Collapse -

by KrizBread In reply to SMALLER .mdb file size???

This question was closed by the author

Back to Web Development Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums