receives the message "AO index is not an index in this
Hi Peter,
This has happened to one of our customers. If you look at the relationships and all the indexes on user tables, you may find that some of them are missing too. You may notice that those missing tend to relate to a specific file.
Since Access won't open the db if AOIndex is missing from MSysAccessObjects, you'll need to open it programatically, with VB or other, and list the relations in the db and the indexes for each table. Do the same with a working copy of the db and compare the results.
I've never found the perfect answer but it may have to do with garbage in a PK. If the db is then repaired/compacted, it is trashed. I think the data is still intact but it probably shouldn't be trusted. I hope your customer has a backup.
Here are a couple links. I think the first one is the key to the problem, at least if you are using an autonumber for a PK. The second is just a good idea, especially if there are multiple computers sharing the db.
http://allenbrowne.com/ser-40.html
http://support.microsoft.com/default.aspx?kbid=239114
Jay