Now just keep in mind, Keith, that "full optimization" doesn't necessarily (any more) mean that you are getting the fastest possible query!!!

There were some long-winded and near-flammable threads on this within the last 3 months.

Jim N

>>Keith,
>>You may want to try an Index on deleted(). If you environment settings
>>have the value set. It's worth a try anyway.
>>
>>Be sure to start including NOFILTER if you are fully optimizing your
>>result sets. It saves alot of time hunting down bugs that will pop
>>up once the results are fully optimized.
>
>I don't understand it, but it sure worked. I indexed on DELETED() and
>all of a sudden I'm getting full optimization. I *will* be asking
>somebody (pro'ly Kevin Levy) about this in Costa Mesa! :-)
>
>Thanks for your help guys.
>
>>
>>
>>
>>>>If SET DELETED is ON, you need an index on Deleted() on both table for a full optimization.
>>>>
>>>>HTH
>>>
>>>Uhhh, no ;-) The file has no deleted records,
>>>and my problem is not partial optimization,
>>>it is *no* optimization for two fields,
>>>Fed_TaxId and Tax_Sufx. It does do partial
>>>optimization for the Code field.
>>>
>>>Thanks for the response though...
>>>
>>> ...kt