>>>Going over the network always presents concerns when doing SCAN-ENDSCANs on a table. All the data has to move over the wire to the local pc to determine if it is in the FOR condition.
>
>>Some people think if you USE a table it's all transferred, but that's wrong. If the FOR condition is Rushmore optimized, the data is also not transferred.
>
>Yes, partially. Rushmore uses indexes to select which records participate in the SCAN, but only for those portions of the FOR clause that can be optimized. If a single SELECT-SQL is performed, then the table is moved in a single "chunk" rather than many small record size "chunks" across the wire. Remember also that Rushmore works in both cases -- my experience is that a single call is faster than lots of little calls to a table for records.

It's not that simple. If you browse for, you are quickly able to browse. If you select where NOFILTER and then wait for the records, you may be waiting longer, even though subsequent navigation may be faster.