Mike and Doris Manning
mikedorism at ntelos.net
Wed Feb 26 14:56:01 CST 2003
There may not be any tables but the bloat still applies... I have one ADP that balloons up to 38MB and then shrinks down to 25MB when I pull everything into a new container. Doris Manning Database Administrator Hargrove Inc. www.hargroveinc.com -----Original Message----- From: accessd-admin at databaseadvisors.com [mailto:accessd-admin at databaseadvisors.com] On Behalf Of Chris Mackin Sent: Wednesday, February 26, 2003 03:34 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Access 2002 database format The first line of the article is: "This article applies only to a Microsoft Access database (.mdb). " AFAIK there are no tables in an .ADP they're all in the SQL backend. Chris Mackin www.denverdb.com Denver Database Consulting, LLC -----Original Message----- From: accessd-admin at databaseadvisors.com [mailto:accessd-admin at databaseadvisors.com]On Behalf Of Dan Waters Sent: Wednesday, February 26, 2003 1:23 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Access 2002 database format If your ADP file contains the hidden table MSysAccessStorage it might be an issue. The KB article describes a way to reproduce the problem. It seems as if it probably will be a problem because the MSysAccessStorage table in their example grew in size when a module was being coded, which happens in the ADP (FE). Dan Waters -----Original Message----- From: accessd-admin at databaseadvisors.com [mailto:accessd-admin at databaseadvisors.com] On Behalf Of Susan Zeller Sent: Wednesday, February 26, 2003 1:16 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Access 2002 database format The article says it only applies to MDB's. Does that mean this is not a concern for ADP files? --Susan -----Original Message----- From: Dan Waters [mailto:dwaters at usinternet.com] Sent: Wednesday, February 26, 2003 8:54 AM To: accessd at databaseadvisors.com 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 -----Original Message----- From: accessd-admin at databaseadvisors.com [mailto:accessd-admin at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Tuesday, February 25, 2003 2:38 PM To: AccessD at databaseadvisors.com Subject: [AccessD] Access 2002 database format Does anyone know of reasons to chose the 2002 format over the default 2000 format, or vice versa, in AXP? I can't think of any reason except to be able to create an mde, which we can't do with our app anyhow because of the design changes it makes to itself at runtime. Charlotte Foust _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com