Cannot repair DB, now what???

[Bernie]

When we try to open a specific Access db, we get an error:
"AOIndex is not an index in this table" then the file
stops attempting to open.

It will not repair (simply returns the same error and
stops). If we go back to the backup we'll lose a bunch of
work done to the interfaces. Lost time and money....

What to do now?

 

[Norman Yuan]

This won't solve your problem, but, you should split your Access db into two
part: backend and frontend, so that the corruption on the backend will not
cause loss of frontend design, there reduce future possible damage.

 

[B.S.Feldman]

Hi,
it's not the univesal answer for your question, but several times I restore
almost all data from the db by linking to it's tables from another MDB file
and then exporting it's data by quries or even (some times) by simple export
table prosedure.

BSF

 

[Jim/Chris]

This is from a previous post

http://members.iinet.net.au/~allenbrowne/ser-47.html

Try Tony Toews' article:

http://www.granite.ab.ca/access/corruptmdbs.htm

and Microsoft Knowledge Base article:

http://support.microsoft.com/?id=209137

or

It can possibly be saved. First, always work on a copy of
the database.
Working on the original may make it impossible for a repair
service to fix
it.

Download a copy of JetComp.exe:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;273956

Also have a look at the Microsoft KB article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;209137

Then have a look at Tony Toews' Access Corruption FAQ at:

http://www.granite.ab.ca/access/corruptmdbs.htm

for some suggestions. Unfortunately, some corruption cannot
be fixed - you
may need to create a new database, import what can be
salvaged, and recreate
the rest.

Although it's a paid service, Peter Miller does an
outstanding job of saving
corrupt databases. Try this URL:

http://www.pksolutions.com

Good Luck

jim