Charlotte Foust
cfoust at infostatsystems.com
Mon Dec 22 16:39:25 CST 2008
Decompile has always been the method of choice for getting rid of pesky
bloat. Just be aware that it doesn't affect some of those hidden system
files added in the later versions of Access. The warnings about
decompile are primarily because Microsoft has always treated it like a
stepchild, perhaps embarassed that it was necessary. It's
"undocumented" in the official phrase.
Charlotte Foust
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Edward Zuris
Sent: Saturday, December 20, 2008 2:56 PM
To: accessd at databaseadvisors.com
Subject: [AccessD] Solution to Access Database Bloat Issue
Here is one solution to Access database bloat issue.
I cam across this solution while looking for an answer to another
problem.
With the example below, a 50 megabyte MDB file went down to ten
megabytes and it became a little more snapper.
1). From the run command I issued the fillowing line.
C:\OfficeW2k\Office\msaccess.exe /decompile
"C:\KateUpload\zEmp027c2.mdb"
2). After the decompile was finished I opened up the Access
MDB file, went to modules. Open one of them modules in
design mode and did a Compile then file on the menu line
and Saved everything.
Going from 50 down to 10 megabytes is a big improvement.
Please are there are warning not to over used the decompile switch.
For more information please look at the following web sites.
<http://www.mvps.org/access/bugs/bugs0008.htm>
http://www.mvps.org/access/bugs/bugs0008.htm
<http://www.trigeminal.com/> http://www.trigeminal.com/
<http://www.trigeminal.com/michka.asp?1033>
http://www.trigeminal.com/michka.asp?1033
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com