[AccessD] Sleuthing - query has become non-updateable

In the start-up form, this should be fairly trivial to check for this
problem via VBA, correct ?

Does it also happen in the case where the primary key is NOT autonumber ?

> I can't tell you why, but every once in a while I have the problem
> where a corrupted row in a table changes the table definition, removing
the
> primary key designation of an autonumber field.  At the same time the
> autonumber value sequence has gone bad, and the database tries to create
duplicate
> autonumber values.  I have had to rebuild the table, as Lambert
> suggests.
>
> Doug