>James,
>
>Do a sys(3054,11) call prior to running the selects and see what it tells you.
>
>>I'd like to speed up my sql select statement and have tried everything I could think of to make it "Rushmore" optimized, to no avail.
>>
>>Here are two sql's, the first is slow, the second is fast.

David, et al,

Here are the results form the sys(3054,11) function.
first sql:
"Rushmore optimization level for table master: none"
'NO WONDER IT'S SLOW'


second sql:
"using index tag yr_bred to rushmore optimize table master"
"Rushmore optimization level for table master: partial"

Okay, now what?

Reversing the order of running the sql's does not help.

The category and type fields are indexed.

I'm not familiar with "INLIST", I'll check the 'help' files for that one and try it out.

I've tried it on both the network and locally and of course the local runs in 10 seconds, the trouble begins on the network, which is where it needs to be.

I did break it down in to more than one sql but that didn't work either.

It's obviously that the sql is not rushmore optimized, finding the solution is harder.

Thanks for the ideas, I'll try them all out and get back.

Jim