Yes, it will replace the key in the index if you delete a record with that key then add a new one with the same key. However, if you have two records with the same key and you delete the one that's in the index it still won't add the other to the index until you REINDEX.

>That's not what I meant. I mean that if you delete the key that's in the index, it is no longer indexed on that key. I'm not sure what it would do if you did UNIQUE FOR !DELETED(). It might replace the key in the index then, but I'm not sure.
>
>-Michelle
>
>>Michelle,
>>
>>That's true. INDEX ON pays no attention to SET DELETED. This can also cause problems with PRIMARY and CANDIDATE indexes. You can deal with this using INDEX...UNIQUE FOR !DELETED().
>>