Doug Steele
dbdoug at gmail.com
Wed Jan 11 16:32:40 CST 2012
Backups: As far as I can remember we did have a backup, but it was at least 24 hours old and the client was reluctant to take the chance of losing a day's work. And I had I initially assured him it would just take a few minutes to fix....The other two times it happened, I figured it out pretty quickly. Autonumber: The situation has only occurred in tables with autonumber primary keys. Doug On Wed, Jan 11, 2012 at 10:02 AM, Mark Simms <marksimms at verizon.net> wrote: > 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 > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >