Error 3800, 'AOIndex is not an index in this table' error message in Access

MS Access is very handy when it comes to storing data in the databases. It's like a one stop destination for many business professionals and personal users alike but what one frequently refuses to understand is the fact that MS Access is not completely foolproof, nothing is, so it's important to remain aware when things don't fall I place as they should.


Error messages impeding proper functioning of MS Access is not uncommon but staying on guard and staying backed up so that no complication becomes big enough to affect a grave damage is definitely uncommon or should I say remote. Data loss stemming from occurrence of error messages can happen, thus it's crucial to identify the issue and act expediently.


Discussed below is one such error message that can wreak real time disaster in your database. Error 3800, 'AOIndex is not an index in this table' is an error message that spells havoc cause its occurrence has a direct co-relation with database system tables corruption. In majority of the cases, gross corruption was at the root of the problem. To put it in simpler terms this error flashes when an index of a system table gets damaged. Some are of the opinion that this error message appears as a "bogus" message in response to another fault or error that is plaguing the system.



This can happen in various instances like


- While attempting to "compact and repair" the file

- Adding a record to one of the tables

- While trying to open the file and many more

Things to try out when you see this error message:


- Try to repair the database and import the tables, modules etc. from another database.

- Try opening a blank database and importing all the objects into it

- Delete the .ldb file with the same name as your .mdb

- Try the Jetcomp utility

- Certain VBScripts allow the database to open in Access and

recreates the table automatically. All you have to do is copy and

paste the VB script into a notepad and save the file with a VB

extension. Remember to change the variable to point to the

path of your database. If you have access to any such VB Scripts, try your luck.


If none of these are working out for you, you are in for trouble and require expert assistance cause corruption left unattended can result in greater damage and irreversible data loss.


If gross corruption has already set in and you are on the look out for an access repair software that can retrieve your precious data, try Stellar's Access Recovery software


Stellar Information Systems Ltd, a pioneer in the data recovery industry with 15 years of experience has devised a data recovery utility for recovering and repairing lost .mdb files. Stellar's Access Recovery software effectively repairs and restores the corrupted access database. It is equipped to deal with any problems that might entail repair of any of the components of the Access database including tables, forms, reports, queries and macros.



The specialty of Stellar Phoenix Access Recovery lies in the fact that it restores the repaired file in its original format that too in its original location. It is capable of effectively handling challenges relating to all possible cases of database corruption.

Author : Spear
http://www.articleclick.com/Article/Error-3800-AOIndex-is-not-an-index-in-this-table-error-message-in-Access/1014939