Hi Evelyn,

I have experienced the same behavior a few times. Oddly, the "missing" record appeared when I updated the table with table buffering ON and issuing a tableUpdate(). I used the same application that was running when the hardware failed.
If the application complains because a PK violation, then modify the table and turn the primary index into a regular one, and go through the updating proccess.
Once the invalid record arises, I recovered the information from it, changed the PK value, and modified the structure to change the index type to primary.

HTH,
Javier.

>Hi, Don!
>
>I am interested if you had resolved your problem here. I am experiencing quite similar problem-VFP tells me that the uniqueness of my pk field is violated but I could not find any duplicates at all. Mine resulted from a hardware failure. My records got corrupted. In some of my files, I could see strange characters in the records at the bottom of the file. I removed all these strange chars, packed the file, and then tried to recreate my primary index key. VFP would not let me because of uniqueness violation. I issued select distinct, select [pk field], count([pk field])... group by [pk field] and found no duplicate. What I even did was I freed the table and generated a candidate index out of the same field and vfp let me. I reincluded the file into my db container and generated a candidate key from the same field and VFP let me as well. All these that I have done so far proved that there wasn't really a uniqueness violation on that field. Why, therefore could I not generate my primary
>key?
>
>It looks like the UT community has run out of answers for me, which is scary. Maybe at this point in time you've already resolved your problem and share it with me?
>
>Thanks,
>Evelyn