NexusDB

"I thought that using: id_object > 110000 and id_object < 110002 as a filter on a table with the SQL filter checkbox checked would result in the same speed as executing a query with select * from objecten where id_object 110000 and id_object < 110002. The latter is much, much faster however (reccount is OFF)."

No, they operate quite differently. A SQL filter is just like any other filter except that SQL syntax is used to specify it.

What this implies is that the engine can't alter the index or any sub-range that the user (EM in this case, from the sound of it) may have selected. On a pure SQL query, however, the SQL engine is completely in charge and can change index and set ranges as it sees fit as long as the query specification is met.