Heenan, Lambert
Lambert.Heenan at AIG.com
Tue Nov 8 13:06:01 CST 2005
Number 1 on the list should always be "Make a backup copy of the mdb" Then... compact and repair Still not good?... Decompile (not officially supported, so make sure you backup) If neither of the above fixes the problem try using JetComp to compact the database. Still no luck? Import everything into a new database. If you think you know that a specific code module is causing the problem then try this. Open the module and comment out all the code lines Save the module Compact and repair Compile Open the module again and uncomment all the code lines Save the module Compact and repair Compile Compact and repair. HTH Lambert -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Hale, Jim Sent: Tuesday, November 08, 2005 1:52 PM To: 'Accessd (E-mail) 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