• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 478
  • Last Modified:

MDB Size After Compact & Repair

Following a "Save Operation Failed" error, I followed instructions found in another EE topic to decompile, re-compile and Compact and Repair the mdb.  This all seems to have worked fine, however, I notice that my mdb is now 1/2 the size it was previous to these procedures.  Having regularly compiled and C&R'ed the mdb, I wondered if this is reasonable... and why?  
0
donthee
Asked:
donthee
  • 4
  • 4
1 Solution
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
Yes ... definitely. It will shrink typically a LOT.

mx
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
Why is because of the 'bloat' factor.  Adding, deleting objects in design, adding code and compiling code, adding data and deleting data ... all contribute to bloat.  C&R gets rid of the bloat.  This has been the case since Access 1.0.

And ... if you ZIP up an MDB ... the ZIP file is even smaller.  

mx
0
 
dontheeAuthor Commented:
thanks for the quick reply.  even if regularly compacted and repaired?  27mb to 13 mb.  is there an explanation why the regular c&r doesn't do the same as the decompile, etc?
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
dontheeAuthor Commented:
and does that mean the proper procedure should be to decompile, re-compile then c&r?
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
Normally, unless you encounter an error such as the one you did, only C&R s/b part of daily maintenance.

Actually, after you Decompile and then recompile ... the mdb will typically be larger.  Then, you do a C&R to bring it back down to the 'normal' size.  Almost anytime you compile, the MDB will get bigger ... due to the nature of how Compile works.

mx
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
You really shouldn't decompile unless you need to do so, or at the very least make a copy before you decompile. You should, however, compact and repair regularly as mx said.

0
 
dontheeAuthor Commented:
one further comment then i'll accept your answers and up the points.  i have been watching the size of this mdb closely and its has been growing slowly in 20 something mb range.  as stated, i have been compacting and repairing regularly (with no recent previous errors) yet today, following the decompile, the size halved.  was something embedded that kept it up at 27mb that the decompile, etc today removed?  i still don't see why the regular, previous c&r'ing didn't produce the same size reduction.
thanks again.
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
According the Michael (aka, Mica aka Micheal) Kaplan ...

"If it works, Don't fix it"

"was something embedded that kept it up at 27mb that the decompile, etc today removed?"

Could *definitely* be the case ... I see that happen often on my MDB's

mx

0
 
dontheeAuthor Commented:
Thanks again, DatabaseMX.
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now