It is optimizable as you have it now. Look in the Help at Rushmore/Optimization for more details.

Vlad

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