>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?
Jeff,

There was a situation in past versions where the syntax of NOT Surpress would not be optimized but Surpress = .F. would be optimized. I think that is no longer true in 5.0 though.

One acution, if you have SET DELETED ON you need an index on DELETED() on every table regardless of whether the table has any deleted records or not in order to get full optimization.