Erik,

That's really odd that you had to build an expression like that into the index.
I wish sys(3054) would tell us more detail about what expression is making the whole where only partially/not optimizeable.

In my case tCreated is a type T field, and ltStart, ltStop are local variables of type T. This table never has deleted records so I SET DELETED OFF before running the select instead of doing a tag on deleted(). It saves a lot of space since this table is millions of records.

>I can't answer you directly, but can relay a recent learning experience I had with Rushmore.
>
>I had a view that that was doing something similar to yours (simpler, actually),
>it was something like:
>
>SELE * FROM BondCard;
>WHERE TimeStamp > WebSent
>
>Where timestamp and websent are datetime fields.
>
>There were indexes on both fields, but SYS(3054) revealed that it was only partially optimized (index on DELETED() too).
>
>I even then created an index on timestamp > websent, and still no optimization.
>To get it to optimize, I had to retain the index on timestamp > websent and restructure the view to read:
>
>SELE * FROM BondCard;
>WHERE (TimeStamp > WebSent) = .T.
>
>Talk about persnickety. BTW, thanks to Barbara P. for the point in the right direction with that one.