>>1. I am accessing the data locally.
>>2. The total number of records is 7,127.
>>3. The speed is approximately 17 seconds with this data set.
>>
>
>Did you tried to delete tags all and add them one by one by adding a new condition? 17 sec. seems too long for me. It should be 1-3 sec. Did you try it on different machines?
>

I have got a 1 gig Athlon with .5 gig of ram. It does seem long to me too. But the counts for each condition are very high relatively speaking. If you can get one condition that narrows to 1000 records or less the speed should be reasonable.


>>>Did you access this table locally or through the network? What's the number of records in a table and what speed do you get?
>>>
>>>
>>>
>>>>SET DELETED is OFF.
>>>>
>>>>The ANSI setting is OFF.
>>>>
>>>>I'm not sure what you are saying about the PADR, but I am willing to try it.
>>>>
>>>>Here are the results of the Sys(3054,11)
>>>>Using Index tag Upperramp to rushmore optimize table vindata
>>>>Using Indes tag HourCount to rushmore optimize table vindata
>>>>Using index tag UpperVend to rushmore optimize table vindata
>>>>Rushmore optimization level for table vindata: full
>>>>
>>>>I have removed the two clauses in the where that were checking for empty.
>>>>
>>>>>Try with SET DELETED OFF to test the speed difference.
>>>>>
>>>>>Also what are the SET ANSI setting? Try to use the whole length expression on the right side, e.g., if Ramp (what is it, BTW?) is 20 chars, you should use variable lcRamp=padr('CHICAGO',20), etc.
>>>>>
>>>>>You can try to drop index keys and run it again. Also show us, what SYS(3054,11) returned.
>>>>>
>>>>>snip<