Indexing Effectively for Rushmore Rushmore cannot take advantage of all indexes. If you use a FOR clause in the INDEX command, Rushmore cannot use the index for optimization. For example, because it contains a FOR clause, the following statement cannot be optimized: INDEX ON ORDNUM FOR DISCOUNT > 10 TAG ORDDISC Similarly, Rushmore cannot use an index created with a NOT condition. For example, the following expression can be optimized: INDEX ON DELETED() TAG DEL But this one cannot: INDEX ON NOT DELETED() TAG NOTDELSo isn't this clear that indexes with a FOR clause will NOT be used by Rushmore to optimize commands?