DELETED files are still in the table so uniqueness is violated. If you pack the table you can then add another key.

A better solution is to automatically generate primary keys that have not been used before in a sequence.

>I am working in VFP 5.0a and have a 2.6 program running. The program is a screen for data entry. When I delete a record the program will mark the record for deletion. That part works great, the problem is when I input another record with the same value in the primary key field I get a "uniqueness violation". I understand that a primary key needs to be unique but why is VFP not ignoring the the deleted records? I used SET DELETED ON in the setup code and within the 2.6 program but it seems to make no difference. How do I get VFP5.0a to ignore the deleted records so that I may reuse a value within the primary key field?