Hi Abel,

> bypass or ignore deleted records?

Why would you need to?

If your problem happens with a PRIMARY index, the right answer would be to introduce a surrogate key (http://fox.wikis.com/wc.dll?Wiki~SurrogateKey~SoftwareEng) instead of using a user controlled field as a primary key. If the error happens on a CANDIDATE index, the FOR clause that Naomi mentioned is the way to go. However, if the field is needed for optimization, you need to add a second non-CANDIDATE index on the same field without a FOR clause just for optimization purposes.