>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

Sorry, but I just thought of something you might be able to do so your chance of seeing this again is minimal (assuming you're not too worried about being able to "recall" data):

In your data controller (the object you use to talk to the back-end), should have a delete method that gets fired whenever you delete a record. Effetively this method should change the value of the candidate key to another sys(2015) value.