>Usually, when I generate a script, the quote character is converted like this:
>
>

>...WHERE Client.City='Michel''s city'
>

>
>That would work.
>
>I can also do this:
>
>

>...WHERE Client.City='Michel'+CHAR(39)+'s city'
>

>
>But, in cases where I need to pass the entire command as a variable, I cannot use the double quote and SQL Server complains if I use this:
>
>

>SET @SQL='...WHERE Client.City=''Michel'+CHAR(39)+'s city'''
>

>
>It does not like CHAR(39) if inserted inside a string which is also inserted inside a string.
>
>Any idea on how to resolve this?

SET @SQL='...WHERE Client.City=''Michel''''s city'''