>But if the deleted()- index slows down other queries significantly, you could

>set dele off
>*-- count with a compound index handling deleted and filter condition
>set dele on

>
>to keep the speed in the count and have no deleted() index. But if the index on the integer filed is used elsewhere, you could have a proliferation of tags, which is bad in itself. As I said, no really *good* choices <g>.

We use the data access from the OleDb provider. So, we need to rely on having a SQL command as is without the need to switch settings like that on every SQL command.