>>This works. But, what does it do exactly?
>
>Uses Belt, Suspenders and Chastity girdle to force a string, as your
>CHAR(34)+'Hello'+CHAR(10)+'World'+CHAR(34)
>worked, but Replace() failed and eliminates side effects perhaps caused by your replace as well
>.
>So using only functions which in wee times of differing SQL dialects either were missing or already were guaranteed to be working on strings only should do the same - if some very old code allowed replace to do other things as well, that might cause hickups or the replacement worked like wrong SQL injection.
>
>Curious minds might now abolish some parts of working statement
>CHAR(34)+substring(" " +Table.Field, 2, 999999)+CHAR(34)
>CHAR(34)+rtrim(Table.Field)+CHAR(34)
>CHAR(34)+cast(Table.Field as ...)+CHAR(34)
>CHAR(34)+stuff(Table.Field, with no working, "whatever")+CHAR(34)
>CHAR(34)+stuff(Table.Field, working, "whatever")+CHAR(34)
>
>to discern a pattern ;-)
>
>Of course sometimes my gut hunches are correct and my mental reasoning after the fact is totally off base. It is a weird way to operate if you are normally proud on the workings of the matter between your ears...

Thanks