[AccessD] Sleuthing - query has become non-updateable

Yes, the table definition change has happened to me at least three times
(in the last 5 years), on two different client databases.  I know this for
sure - I had the worst day ever in my programming career the first time it
happened.  My client had about 10 employees sitting on their hands, he was
frantic, and I was working on a laptop away from my office.  It took me
nearly a full day to figure out what had happened, as, of course, I never
thought of checking the actual table definition.  No table related to the
corrupt table would update, as the relationships had disappeared.  I just
assumed I had a bizarre multi table corruption issue.  Once I saw what the
problem was, I was able to remove the bad duplicate key records, force the
autonumber back into sequence, restore the bad records, make the field a
key again and restore the relationships.  I didn't have to fully rebuild
the table, fortunately.

Doug

On Wed, Jan 11, 2012 at 9:07 AM, Heenan, Lambert <
Lambert.Heenan at chartisinsurance.com> wrote:

> 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
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>