<< I recall that the last time I had a query where I did this sort of thing
it defaulted to a row scan because of the True/False parameter. Has this
changed? >>
Yeah, I think you're right, but it isn't because of the True/False
parameter - it's the OR linking together two = conditions from two different
tables.