I just got a new clue to this puzzle. A friend tested the same scenario on another server in another company and DID NOT GET THE ERROR! It doesn't solve my problem but it is pretty datned interesting academically.

Bob




>The SQL Server Books Online does a pretty good job on this topic. Check out the section on Delimited Identifiers and SET QUOTED_IDENTIFIER. Here's a section from the Books Online:
>
>When QUOTED_IDENTIFIER is ON, SQL Server follows the SQL-92 rules for the use of double quotation marks and single quotation marks in SQL statements:
>
>- Double quotation marks can be used only to delimit identifiers. They cannot be used to delimit character strings. To maintain compatibility with existing applications, SQL Server is not rigorous in its enforcement of this rule. Character strings can be enclosed in double quotation marks if the string does not exceed the length of an identifier; however, this practice is not recommended.
>
>- Single quotation marks must be used to enclose character strings. They cannot be used to delimit identifiers. If the character string contains an embedded single quotation mark, insert an additional single quotation mark in front of the embedded mark:
>
>SELECT * FROM "My Table"
>WHERE "Last Name" = 'O''Brien'
>
>
>When QUOTED_IDENTIFIER is OFF, SQL Server follows these rules for the use of double and single quotation marks:
>
>- Quotation marks cannot be used to delimit identifiers. Instead, use brackets as delimiters.
>
>- Either single or double quotation marks can be used to enclose character strings. If double quotation marks are used, embedded single quotation marks do not have to be denoted by two single quotation marks:
>
>SELECT * FROM [My Table]
>WHERE [Last Name] = "O'Brien"
>
>To solve your problem, you'll need to SET QUOTED_IDENTIFIER OFF. Unfortunately I'm not sure where you manipulate this setting.
>
>-Mike