Nightly Access 2003 Corruption

[squiggly12]

For the past two nights, our access application that is in 2003 is becoming corrupt. When I have done a comparison of the corrupt database, and a working copy on my local machine, I see several queries that are gone. All other forms, reports and macros are still there.

This has me very confused as this just started happening, does anyone have any insight as to why this is happening?

[eskelies]

Here are a few issues I know of:

• Interrupted write operation
• Faulty networking hardware
• Opening and saving the .mdb file in another program
• Mismatched Versions of the Jet Database Engine
• multi-user access
• Inefficient database design

For the past two nights, our access application that is in 2003 is becoming corrupt. When I have done a comparison of the corrupt database, and a working copy on my local machine, I see several queries that are gone. All other forms, reports and macros are still there.

This has me very confused as this just started happening, does anyone have any insight as to why this is happening?

[fyz]

For the past two nights, our access application that is in 2003 is becoming corrupt. When I have done a comparison of the corrupt database, and a working copy on my local machine, I see several queries that are gone. All other forms, reports and macros are still there.

This has me very confused as this just started happening, does anyone have any insight as to why this is happening?

Hi,

If the methods above do not work, you may try Advanced Access Repair at http://www.datanumen.c om/aar/ This tool is rather useful in salvaging damaged Access MDB files. Hope this helps.

Alan

[missinglinq]

Is there any process that is being carried out every night? Using "Compact and Repair on Closing" has a reputation of being a source of chronic corruption. which is why
C & R shouldn't be used without backing up the database first.

Also, since this happens at end of day/night, has someone become too lazy to exit Access correctly, instead simply turning of their PC? This, too, is thought by some to cause corruption.

Linq ;0)>