>Sylvain, the other suggestions are excellent, but in addition I have noticed that a SELECT slows down when you have a parent/child/grandchild relation (in yours you have MemberList, ProductList, Supplier.
>
>My solution is to break the list into 2 Select commands. In one case the time spent went from 6 minutes to 1.2 seconds. In all my test cases my SELECT reported fully optimized as yours does.

Since I will be creating an index for each field of the resulting query anyway {another slowdown :(}, I will try out your suggestion.

Thanks for your help