# 834 OnFilterRecord Callback Filters not Being Applied After Other Filters in Some Cases

---

A short while ago, in February, I asked if the OnFilterRecord respected the Filter property. You said it didn't but could make it so. This seems to have been done as the speed for filtering when both are involved is much faster. I seem to having a problem with this now. I set the filter on Manufacturer, then set Filtered to true. There is an OnFilterRecord defined as well. This takes only a few seconds when working against a table with 270,000 records. In the OnFilterRecord event, I am writing the manufacturer code to a label caption, if the record being tested does not have the same manufacturer as the one used for the filter property (just for testing purposes). The filter is executed when the user clicks the Next button (after specifying the manufacturer) and going to the next page which has the grid. This happens fast and the label does not display anything, so this works fine. In the grid, the user can then modify a records Quantity column (it's a stock take variance form). This modification, may mean the record now falls
outside the filter criteria as defined in the OnFilterRecord event. When the record is saved, the filter is reapplied, however this time, the OnFilterRecord event goes through all 270,000 records, and does not respect the filter property. I have tested the Filter property in a debug session and the filter property value is still set correctly.