[AccessD] Sleuthing - query has become non-updateable

Me neither. I've certainly seen examples where the PK seed gets corrupted and then Access tries to assign an existing PK value to a new record, at which point access complains of a duplicate value. So that would indicate that the PK status has stayed in place. 

Lambert

-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Wednesday, January 11, 2012 11:55 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Sleuthing - query has become non-updateable

Hi Doug

.. 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.  

Is that really so? I've never seen that.

/gustav


>>> dbdoug at gmail.com 11-01-2012 17:18 >>>
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