[AccessD] Decompile

Another thing to try on the offending objects....

Strip all of the code from them if you can.  (If you can't, this won't work.)
Paste the code into Notepad if you can.

Repair and compact the database, then decompile and recompile.  Then paste
your offending code back into the object's modules.  Then recompile.

I've saved at least one database this way.

HTH,

Steve

-----Stephen Pickering's Original Message-----

Mark,

Import every object except the corrupt ones.  If you don't have a version of
these objects that isn't corrupt, you will need to rebuild them.

Also, back up early and often.  Corruption happens.  It's sometimes, but not
always, because of something you've done.  Best to be prepared.  Some
databases never come back....

Steve

-----Mark S. Mitsules' Original Message-----
From: Mitsules, Mark S. (Newport News) [mailto:Mark.Mitsules at ngc.com]
Sent: Thursday, April 15, 2004 2:40 PM
To: '[AccessD]'
Subject: [AccessD] Decompile


Has anyone seen a case where /decompile did not appear to do anything?  I'm
getting the same "corrupt" error message as before.  I have 2 objects that
appear to be the culprits.  I get the same "corrupt" error message when
trying to import these objects into a new database (no error messages on the
other objects).  In the corrupted database I cannot go into the IDE at
all...I get the same "corrupt" error message.  This is actually the first
time I've been bitten, without having a recent backup to fall back to, and
I'm stressing.  Any suggestions?



Mark
--