Table repair utilities primarily only repair a table header so that it will be recognized as a VFP table again. These utilities normally do not fix bad data [offsets].

I would think that once you deleted the garbage data and packed the table, your problem with PK would clear up. Or at least you would be able to more easily find duplicates.

>Can someone please tell me what happened under the following senerio:
>1.On a stand alone test machine when running the stonefield repair program I received an error message 'Primary key violation' or something to that effect.
>2.On my development machine, using the same data, I was able to use the table and examine it for duplicate records. I did not find any.
>3.I then on the development machine ran the app and ran the stonefield repair program. I got the same message as in #1 above.
>4 When I returned to the command window I dropped the table from the DBC and browsed it. The table is toast- there is garbage and what date there is is offset.
>
>Any help greatly appreciated.
>By the way, what does one do to fix a primary key violation that is already in the table???