>>This select takes very long time if there are many records returned.
>>set filter works much faster since it will not scan whole table.
>>Also this does not change base table.
>>I want to edit data in large table where records are filtered
>>by an arbitrary (rusmore optimizable because there are some indexes) condition.
>>I want to edit filtered records in a grid.
>>
>Well Andrus. OK but is there something new with "set filter" that I don't know. Set filter works much faster than SQL select ? I always thought it was not the case. I should check this again and if true thanks for warning about it.

Searching data with set filter and sql select works at same speed I think.

However, searching data with set filter and grid works very slowly,
since grid refresh seems not to use rushmore optimization with set filter,
it likes to scan all records (seems to be bug also noted in the visual extend manual but not in any other places).

"browse for " works also fast, since it uses rushmore, but this is not oop.

So my problem is to find a alternate way to set filter + grid control for
arbitrary search expression. set key needs pre-determined search expression,
create sql view scans whole base table.
There seems no way to do it and i'm very unhappy.

Andrus