D Cook
dbcfour at triad.rr.com
Sat Mar 1 14:26:01 CST 2003
Posted on behalf of William Hindman, who's posts don't appear to be making it through. Donna ...there is a problem with bloating in the XP storage format ...creating an empty mdb and importing everything into it will get rid of the bloat ...MS will get around to fixing this sooner or later :( ...in the meantime, since I do require mdes, I'm stuck with the XP format ...so far the bloating, now that I can fix it easily, isn't a major problem ...but if I didn't require mdes I'd be using the 2K format. ...there appears to be VERY little information available on the differences other than some vague reference to the XP format having some features applicable to future Access versions and supposedly more efficient storage ...considering the definite bloat problem, I have issues with the MS definition of "efficient" :( William Hindman ----- Original Message ----- From: Dan Waters <mailto:dwaters at usinternet.com> To: accessd at databaseadvisors.com <mailto:accessd at databaseadvisors.com> Sent: Wednesday, February 26, 2003 9:54 AM Subject: RE: [AccessD] Access 2002 database format Charlotte - Here is something to be aware of. Microsoft Knowledge Base Article - 810415 Access 2002 Format Database Bloat Is Not Stopped by Compacting <http://support.microsoft.com/default.aspx?scid=kb;en-us;810415> The KB article describes a system table in XP that is not compacted when it should be. Microsoft confirms that this is a problem and they recommend developing using the 2000 format when you can. I was developing an ~ 15 Mb database in 2002 format, but it bloated to 3 - 4 times this size, and decompiling/compacting didn't shrink it. I moved all the objects to a 2000 db file, and then was able to get it back down to the normal size. Dan Waters --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.459 / Virus Database: 258 - Release Date: 2/25/2003