>What do you mean with the point 2)?
>
>Vlad
>
>>Whenever you set filter you need to...
>>1)Ensure that you have an index on the field you are filtering
>>2)set order to 0, otherwise you essentially get 2 filters fighting each other
>>3)if you have set deleted on, you should have an index on deleted(), something like "INDEX ON DELETED() TAG ISDELETED"
>>
>>In most cases it is better to use an SQL Cursor for most filters.
>>
>>Hope this helps //:^)
What I mean is that since Rushmore uses the available indexes to determine which record to go to next, a filter on one field with an active index on another field makes the system have to parse thru two indexes at the same time, which in my experience greatly slows down the searches.