>Daniel,
>
>>I assume that each of the fields being joined and/or filtered on are indexed (including deleted). If not, that may also help.
>
>Indexing on DELETED() is seldom a good idea. Actually this might be Nadyas problem. Indexes on deleted() on large tables create a massive overhead which might be very well the cause of her problems. It's generally proven that DELETED() tags almost never helpfull in gaining performance, but could make you app terrible slow.
>
>Walter,

Damm, looks like I've got some changes to make. Still, my first idea, back at the begining of this tread, to split the query up, seems to have been the solution...