Characters that SQL Server does not like

[awhitsel]

I am working on a VB program that is using several SQL statements intermingled into it.

On of these statements is taking exception to a statement in a VB text box.

At my last job, I was told that there certain characters that SQL Server just doesn't like, such as apostrophes (which is what this statement had), but there others, such as hyphens and double quotes.

Could you please confirm this problem with apostrophes, hyphens, and double quotes?

Thank you.

 

[JayKusch]

Need to see the code that is handling the text from your text box. The " and ' may be the culprit.

Thanks

J. Kusch

 

[SQLBill]

It's not that SQL Server doesn't 'like' certain symbols, it's that SQL Server uses them for something other than what they are grammatically meant for.

For example: an underscore (_) is used as a wild-card in SQL Server. Same with the percent sign (%).

Single apostrophe is used to mark text (ie CHAR/VARCHAR). Example: WHERE myfield = 'Hello'

-SQLBill

 

[awhitsel]

JayKusch: Here is the code where the problem is occurring:

strSQL = "UPDATE CY48_REPORT_A SET INJURIES='" Trim(ml_conditions.Text) & "' WHERE SESSION_ID=" & lf_session

For security reasons, I an unable to show you the actual statement in the text box, but what I am able to tell you is that one of the statements contains an apostrophe and two commas. The second statement contains two double quotes, and a hyphen