>CHR(34) produces a double-quote. You need to use a single-quote. The double-quote has special meaning to SQL Server.
>
>-Mike
>
>>I wrapped it with CHR(34) instead. The data has apostrophes embedded in the data.

Can you tell me what the special meaning is that double quotes have with SQL? I seem to be able to pass double-quoted parameters to stored procs readily. Also, if I use a single quote, I get an error when the DDQ comes across a record with an embedded apostrophe. Can I use the backward apostrophe in the upper left corner of my keyboard?

:-)

Bob