ID is not an index in this table

[Bart]

Have created a database in Access 2007 (2003 fomat) which runs on 2003.

One datafile containing all tables and data, and a 'program' mdb file
containing the forms, reports and VBA code, having links to the tables in the
data file

After a while the progam file starts up with the message "ID is not an index
in this table" while ID is not in use in my own tables.

Looks to me that somehow one of the system tables gets corrupted. Wondering
which system table... and more wondering WHY it get corrupted

Replacing the 'program' file with the original version solves the problem,
so the problem is definitely not in the data file.

Compact and repair of the 'program' file does not help. Creating a new
database and try to import the data from the corrupted file ends up in a
endless loop of message boxes showing "ID is not an index in this table".
This required a hard stop of Access.

Any known problems causing table corruption in Access 2003 with a database
developed in Access 2007 in 2003 format ?

 

[John W. Vinson]

Any known problems causing table corruption in Access 2003 with a database
developed in Access 2007 in 2003 format ?

Yes. <g>

See http://www.granite.ab.ca/access/corruptmdbs.htm for a thorough discussion
of database corruption issues.

John W. Vinson [MVP]

 

[Bart]

Yes. <g>

See http://www.granite.ab.ca/access/corruptmdbs.htm for a thorough discussion
of database corruption issues.

John W. Vinson [MVP]

Thanks John,

Any plans from MS to solve the sudden corruptions in Access ?
The link you sent I had read before I posted and searched the
news groups. My user(s) don't like to solve and repair databases
they want to use it for their data earning them money.

Any solutions to prevent (!!) these corruptions from happening
would be apreciated

Regards

Bart

 

[John W. Vinson]

Thanks John,

Any plans from MS to solve the sudden corruptions in Access ?

Well, I don't work for MS and don't have an inside lead to their planning, but
I'm sure they don't approve of them.

The link you sent I had read before I posted and searched the
news groups. My user(s) don't like to solve and repair databases
they want to use it for their data earning them money.

Any solutions to prevent (!!) these corruptions from happening
would be apreciated

Other than the preventative measures Tony suggests... nothing in particular.
Split your databases; use tested, compiled MDE's as frontends; Don't let
users share frontends; use good solid NIC's on your network; and keep good
backups.

John W. Vinson [MVP]