---

 Comments

---

The problem was caused by the internal NOTing of bitmaps, which resulted in deleted records showing up in the results. This fix does have one somewhat negative side effect in that it causes NOT filter or query expressions to be handled in a partially brute-force fashion. This was unavoidable, since the it is the only way to handle removing deleted records from the bitmap generated by the NOT operation. This does not, however, apply to individual operators like <>, NOT LIKE, NOT IN, or NOT BETWEEN. It only applies to expressions like NOT (expression AND expression). These types of expressions can usually, but not always, be re-worded in a more optimal fashion.

---

 Resolution

---

Fixed Problem on 4/26/2004 in version 4.06 build 1