>>Right, but what again is the problem? You seems to be answering yourself and not me.
>
>The initial syntax was targeting a char field and was causing the problem. As Subject_E is a char field, the replace can be used as is without a cast. This was a bad cut & paste and it led to confusion. The original code was put back and still works. Body_E is the Varchar(MAX) field and that one is working with the usage of cast.
>
>Thanks

If Body_E is the varchar(max) column, you don't need a CAST.

If it's Text column, it needs a cast (one way only). In both cases the replace will be case-insensitive unless the column is defined with case sensitive collation.