>Hi all,
>
>In the good old FoxPro for DOS days I was used to always
>creating an index on DELETED() in order not to display
>deleted records.
>
>I now want to use instead the FILTER field available in the Table
>Designer to have in there the !DELETED() clause in order to
>achieve the same thing. Does anyone know if there are
>performance penalties associated with using filter clauses
>in index definitions ?
>
>Thanks in advance.
>Michel.

It's enough to mention that 'filtered' indexes cannot be used in Rushmore, i.e. potential penalty is huge.