William Hindman
wdhindman at bellsouth.net
Tue Nov 8 14:27:41 CST 2005
Jim My routine for a "flaky" mdb: ...backup ...save ...compile ...Access compact&repair ...decompile ...Jet Compact Utility ...and when all else fails, rather than the normal import to a new mdb, I try this first: http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='EATBloatV2.mdb' ...its worked wonders for me. William ----- Original Message ----- From: "Hale, Jim" <Jim.Hale at FleetPride.com> To: "'Accessd (E-mail)" <accessd at databaseadvisors.com> Sent: Tuesday, November 08, 2005 1:51 PM Subject: [AccessD] Best way to fix database > Is this the correct order of operations to fix a flaky mdb? I can't > remember > what order works best. > > decompile > compile > save > compact and repair > import to new container > > TIA > Jim Hale > > *********************************************************************** > The information transmitted is intended solely for the individual or > entity to which it is addressed and may contain confidential and/or > privileged material. Any review, retransmission, dissemination or > other use of or taking action in reliance upon this information by > persons or entities other than the intended recipient is prohibited. > If you have received this email in error please contact the sender and > delete the material from any computer. As a recipient of this email, > you are responsible for screening its contents and the contents of any > attachments for the presence of viruses. No liability is accepted for > any damages caused by any virus transmitted by this email. > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >