Hi Michel ----

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

Why do you want to do this? Just create an index tag on DELETED() and forget filters. To quote a certain South Park character, "Filters are bad, OK?" (Sorry -- I know you may not get the reference).