Cristof,

>>In some multitable query's or Relations the performance could benifit by a index on deleted(). If tables contain more than a few deleted records and are joined with eachother in a Query, the performance COULD be tuned with a index on DELETED().

>I don't know about your applications, but in my application I use many selects that involve several tables. Also, I use a lot of Selects that return filtered sets, because I have to process a number of records. Here I don't want to create a physical table. In most of these Selects, an index on DELETED() improves performance in my applications.

I indeed do use multi table queries. But as i stated here it really depends on the number of deleted records here. The same also applies to single table queries.

The line: 'In some multitable query's' may be refering to your example in the other thread. But see my comment there since there is a lot to say about your example.

Walter,