Repair Database Error -- 'AO Index' is not an index in this table

[Guest]

I am unable to open my database. It is composed of queries, forms, and
reports; it is linked to another database which contains all the tables.
I have tried to repair the databse, but I get the following error statement:
"'AO Index' is not an index in this table".
Any ideas what I can do?

Thanks,
Jonathan Mulder Durham, CA

 

[Dirk Goldgar]

I am unable to open my database. It is composed of queries, forms,
and reports; it is linked to another database which contains all the
tables.
I have tried to repair the databse, but I get the following error
statement: "'AO Index' is not an index in this table".
Any ideas what I can do?

Thanks,
Jonathan Mulder Durham, CA

Tony Toews has compiled an exhaustive page on MDB corruption, its
causes, symptoms, and recovery procedures. Look here:

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

 

[Guest]

Thanks for the suggestion; I have looked at his site.

Based on other postings, it seems that this error message appears when the
MSObjects.mdb (or a name close to that) is missing. This database is a split
database composed just of forms, reports, and queries; the data file is in
another database. This file that I cannot repair is fairly critical because
it has modifications to several forms that would be hard to duplicate
(several days work).

Any other suggestions on how to repair this database?

Thanks,
Jon Mulder Red Bluff, CA

 

[Dirk Goldgar]

Thanks for the suggestion; I have looked at his site.

Based on other postings, it seems that this error message appears
when the MSObjects.mdb (or a name close to that) is missing.

The MSysObjects table, maybe?

This
database is a split database composed just of forms, reports, and
queries; the data file is in another database. This file that I
cannot repair is fairly critical because it has modifications to
several forms that would be hard to duplicate (several days work).

Any other suggestions on how to repair this database?

What did you try? Tony lists a number of approaches, and Allen Browne
(linked from Tony's site) has some here:
http://allenbrowne.com/ser-47.html .

The first things that are usually suggested are:

1. Make several copies of the database and work only on a copy!

2. Try the JetComp utility (on a copy).

3. Create a new, blank database and try importing all objects from a
copy of the bad one. If some objects import and others don't, import
the objects one at a time and skip the ones that won't.

The last resort usually suggested is:

Contact a professional repair service of good reputation, such as

PKSolutions
http://www.pksolutions.com/

or

EverythingAccess
http://www.everythingaccess.com/

 

[Guest]

Thank you for those tips. I have tried the JetComp utility, but can't get it
to work on ANY database file (corrupted or not!).

Actually, I am using the Database Compact Utility 4.0, which I downl;oaded
from Microsoft. The Word file that accompanies it, says that it will fix my
problem about the missing AO Index files.

When I press the "Compact" button on the JetComp utulity, I get an error
message box saying "Error compacting database".

Would anybody be willing to try a copy of this file on their computer and
see if it can be repaired?

Thanks for the help and suggestions! Hopefully, I'll get it repaired!

Jon Mulder

 

[Dirk Goldgar]

Thank you for those tips. I have tried the JetComp utility, but
can't get it to work on ANY database file (corrupted or not!).

Actually, I am using the Database Compact Utility 4.0, which I
downl;oaded from Microsoft. The Word file that accompanies it, says
that it will fix my problem about the missing AO Index files.

When I press the "Compact" button on the JetComp utulity, I get an
error message box saying "Error compacting database".

Would anybody be willing to try a copy of this file on their computer
and see if it can be repaired?

E-mail it to me -- zipped, please -- and I'll have a go at it in my
spare time. I'm not promising to get to it immediately, though.

Don't send it to the reply-address of this message; remove "NO",
"SPAM", and ".invalid" from that address, or get my real address off my
website, which is listed below in my sig.

 

[aaron.kempf]

don't use MDB for anything; it is obsolete.

Access Data Projects don't have random bugs like this.

-Aaron

 

[Dirk Goldgar]

E-mail it to me -- zipped, please -- and I'll have a go at it in my
spare time. I'm not promising to get to it immediately, though.

Jon -

I've managed to at least partially repair your database, by deleting
records from the MSysAccessObjects system table that had Null in the
Data and ID fields, and then creating the AOIndex index for that table.
I've e-mailed you the repaired version. I'd be very surprised to find
that nothing has been lost from the "fixed" copy -- and I certainly
wouldn't want you to try to run with it -- but I hope that you can get
your recent modifications from it and put them into a backup copy. If
you can do that, I would definitely then proceed to import all the
objects from the resulting, restored version into a new blank database,
and use that for going on with.