Hi, we've had similar problems with collations across different data sources, but have also found one bonus. As part of the validation for data imports we check for personal info...

You could also try the COALESCE function. I've found it handy for CSV building.

This assumes that tk_number is a varchar, you may have to CAST(tk_number as varchar)  otherwise.

DECLARE @List varchar(2000) 

 SELECT...