>If you say so, but that is not the way I read it

I forgot to mention that the Member.Numero=1, last condition at the end of that select command, was to associate everything against one specific member. I also tried to create a scenario which differs a lot from the real select command I have, which is much more complex. So, at the same time, I tried to make the sample as small as possible.

It turned out that everything is working very well as is. On the first round of test, there was a factor that was not taken into consideration. But, after having looked more into it, that intersect is actually in deed bounced off the main result of the first and last name results. So, I could have 10 Member records found where either the first and last names match, but only 9 would be returned at the end based on the intersect.