It seems a shame to have to create these two new indexes just for this one SQL query, when you already have one index which should be usable. Have you tried the SYS(3054) function to determine if it is optimizing using the custID + poNum index? This might shed some light on things.

>>If the original index wasn't filtered, you should have been able to use it for optimization rather than creating two new indexes on your table. Oh, well, at least you have it working now.
>>
>
>I would rather not have to add the 2 additional indexes. I have INDEXSEEK elsewhere on the the index key I already had, so now I have 3 indexes doing the duty of one. Original index expression is simple: custID + poNum. No filter. Should I not need individual indexes?