Dragan,

I didn't figure out the problem with indexes, but at least I found why SQL produced an error. I fixed the offending code...

Thanks for your help.

>>Ok, mystery continues :) I added Force clause in my Select expression and now it uses code tag to optimize Join condition. The SQL runs much faster (but still not fast enough, I think). The interesting fact is we're using Novell here at work. My colleague tried this SQL on her machine, where she uses NT. Without Force just by changing the order of joining expressions she achieved the significant speed increase and index code was used in optimization. Therefore, I conclude, this SQL is OS dependable! Very strange...
>>
>>I don't have reasonable explanantions here. But this is not the end. If I run this SQL from our menu with Show optimization plan turned on, this SQL produces an error after it finishes. If it's turned off, it goes smoothly... I tried to debug this problem the whole evening, but didn't find an answer yet...
>>
>>Thanks in advance for any clues...
>
>Clueless. You're already in the waters where I didn't try to swim yet. Best of luck :)