>One problem occurs if you use primary or candidate indexes. Since the deleted record is still indexed trying to add a new record that duplicates a key value of a deleted record will cause an uniqueness violation error. This is a problem if a user deletes a record by mistake then tries to add a new record to correct the error. Using surrogate keys is the best way to avoid this problem.

This is very helpful for a couple of reasons. It warns me what to look out for in the future and, you may have just solved a problem my friend has had literally for years with deleted/readded records that spontaneously disappear from a table. Not sure if your example applies to the old Foxpro 1.x stuff but what you describe sure sounds familiar. At least its another angle to check out. Thanks Steve.