>I have a table that has a candidate index on a field named "project." Every once and a while though, the data entry associate accidently saves a blank project entry. Therefore, whenever he tries to add another record and APPEND BLANK kicks in, there is an immediate error that states the uniqueness of index is violated. All that makes perfect sense--however, after deleting the record from the form itself, it still keeps giving the same error. The data control options are set to "ignore deleted records" and the only way to fix this is to actually take exclusive control of the table and purge the record marked for deletion. Any suggestions on how to fix this? Thanks so much in advance. BTW, I'm using VFP 6.0

Basically your problem is this:

You have a Candidate key field, but no default value for it. Therefore, if at any point in time after you create a new record, the users' system bombs, it leaves a blank record in the table. And the behavior you're experiencing is correct: a record still exists (it just happens to have the deleted flag "tagged") so it and any other records must still meet your CK rules.

Use a sys(2015) function for the default value in your CK field. That will take care of it.