[AccessD] How to repair corrupt database

In the past, I would import into a new database only those items I knew were
good. In this case, import everything except the reports. Then see if you
get compile errors. If it compiles correctly, make a backup and then start
importing only those reports that you know are good. I would always save a
backup copy of each of the databases that compile correctly before importing
additional objects. Keep importing more reports until eventually, you'll try
to import a bad object and the database will be corrupt. Then you'll know
which report(s) is causing the problem.

That's the only way I have fixed the problem you're having.

John Skolits


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Janet Erach
Sent: Tuesday, May 29, 2007 2:04 PM
To: accessD at databaseadvisors.com
Subject: [AccessD] How to repair corrupt database

We use a third-party database in Access 2003 in to manage our customer and
sales data.   This morning I was importing a report from a "storage"
database, and accidentally selected an extra report that I did not want.
When I noticed this extra report - call it reportX -  was being imported, I
hit 'cancel'.  And now my database is corrupt.

 ReportX does NOT show up on the reports tab.  It does, however, show up in
the modules project window, and I can even view the code attached to it;  I
cannot delete it, though.  If I try to 'trick' the app by creating a dummy
'ReportX' I get the message that 'ReportX' already exists.

 This is what I've tried so far:

 1) Decompiled the app several times, then tried to recompile.  I get
repeated errors that 'ReportX you entered in either the property sheet or
macro is misspelled or refers to a report that doesn't exist.'  After 4 or
five of those, I get 'Compile error: Module not found'.

 2) Compact/repair the database - access crashes.

 3) Running Jetcomp - error compacting database

 4) Create an empty database - import everything.  Although the import still
complains about missing 'ReportX', it seems like I'm able to successfully
import everything else.  But I can't run the app because I get weird compile
errors like 'variable not defined' or 'user defined type not defined'.  This
app is so dang convoluted to begin with that I don't even know where to look
for the basis of these errors.  It may even have to do with the fact that I
have not properly registered this version of the app - the first time you
run the installed app, it's supposed to detect your registration status and
prompt you from there;  I don't know if there is a 'manual' registration
option.

 Is there anything else I can do to save the database?   ANYTHING??

 Thanks -

Janet Erbach
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com