>I have a 100,000+ record table with no delete() index and my speed of a SQL with "Where !delete()" is very quick, I really believe that it is not needed.
>
>as always I am not the GURU but I don't see a dramatic improvement with the delete() index and a extra index (CDX) slows down the load of every index (CDX) cause all indexes (CDX) for a given table are stored in a single cdx i.e. table1.dbf, table1.cdx stores all indexes for table1.dbf
Not only is the index not needed, but it would actually slow the query down (details in my recent entry in FAQ). Try it, just for fun! Actually, supposing you have an index on DELETED(), the query would only slow down if you combine "AND NOT DELETED()" with another condition, that selects only a few records. By itself,
BTW, you don't need to add "...and not deleted()". This condition is implicit if you issued SET DELETED ON.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
