>I have also seen this in my PK fields on occassion. I am not sure anyone can give you a definitive answer as to why or what caused it. Somewhere along the tableupdate process, data corruption occurred which trashed your PK index and the value in the PK field.
>
>About all you can do is correct the data in the PK field and recreate the PK index. Also correct the last ID used in your counters table. If the PK is also a FK in other tables, you will have to check those child tables to correct any RI issues.

Hi Mark,

That is what I did. Bummer it can't be avoided. Tell me, once we finnaly get all this switched to Oracle. Will this be eliminated?

TKS
Mike