there is no problem with using NOT in the WHERE clause , you can't use NOT in indexes (and have the rushmore optimizable) IAC, you can use SYS(3054) to check if your SELECT statements are optimized and to what extent Arnon >In this VPF 5.0 app, the client does not delete records (legal reasons). >In each table is a logincal filed called SUPPRESS. If it is TRUE, the >record is suppressed (should not be included in SQL). I use SQL's to >populate grids in forms, so I need FAST operation. There is in index on >Suppress In the SQL, if I add " WHERE !SUPPRESS", will it be Rushmore >optimized? I once heard that .not. clauses are not optimizable. Or should >I change the meaning of the SUPPRESS field, so that a TRUE in SUPPRESS >means include, so the WHERE clause can be "WHERER SUPPRESS". Is this >optimizable? > >