HOWEVER (!),

running the UNICODE() comparison again, i see that i overlooked one spot (over hundreds of characters) where 13 <> 32 (carriage return and a space).

/bangs head....

thanks,

yes, i just completed testing with the UNICODE() function, basically checking each column character by character (where Table A's column cast to nvarchar).

And all characters have return...

that's a valid question! and all data being queried are within database using the Latin1_General_CI_AS collation.

so no, nothing's case sensitive. but because i'll try anything at...

bingo...

i'd forgotten there was a scrubbing statement that removes rows from the comparison table where the keys were null.

thanks for dope slapping me 😀

- b

turns out the spaces in between the words in tbl1 were char(10) values, which are not the same as ' ' characters. a replace statement in the selection query...

Hi guys, thanks for the quick replies. I believe the above quote is the answer i was looking for. I'd never seen...