Oh, of course! Thanks Albert.

I finally just added a field for a 'real' unique key, used SYS(2015) for the default value, and made it the primary key, instead of the crazy concatenated key it used to have. All my problems went away. Good database design wins again.

Thanks again.

>Deleted records are still in the index and can potentially be recalled. That is why the exception is thrown. You could trap the error, move to the deleted record, recall it, and overwrite the data.
>
>>That makes sense. But it still seems odd to me that it would complain even though the 'duplicate' record was tagged for deletion. I even tried putting a filter on the primary index for NOT DELETED(). Guess I'll have to bite the bullet and implement a good table design. :) Thanks for your help!
>>
>>
>>>Beth,
>>>
>>>Uniqueness of indexes and valid rules on fields and records are evaluated when you update the buffer. You need to insure that the PK memvar is unique before you issue the INSERT INTO to avoid the error.