>if this is indeed the case you can reverse the use of deleted and use
>the delete flag to mark active records (because !deleted() is not optimizable and deleted() is )
>this way when u do SELECT .... WHERE DELETED() ...
>it will be optimizable (if you have an index on deleted)
>
>Arnon

Is this performance problem related to SELECT-SQL only or to regular table opening/skipping/using as RowSource too?