# 3351 Adding Expression Filter to a Sensitive Query Result Set with RANGE Clause Causes Incorrect Results

---

I'm using Elevate 2.04B4 and seeing some weird behaviour when combining a RANGE clause with a dataset filter.

Lets say I have a 1000 product records where the ProductName begins with 'L' - see below query. You can make an assumption that a single product can come from multiple suppliers.

I'm trying to locate the first record where PreferredFlag = True (in the ProductName,SupplierName order). So I apply a dataset filter (PreferredFlag = True), go to the first record, take a bookmark, remove the filter and go to that bookmark.

However, if the first preferred record is outside of the 1 - 200 range of the original recordset, the GotoBookmark fails with a message - Record not found

Apparently elevate applies the range AFTER filtering the records. What I'm saying is that by applying the filter I suddenly find records that were not in the original range.