Re: Msg 207, Level 16, State 3, Line 1

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

On May 27, 5:05 pm, Plamen Ratchev <Pla...@xxxxxxxxxxxxx> wrote:
I meant to run the script in SSMS query and look in the messages pane to
see the actual statement being executed (you would have to define the
variables and set them correctly).

--
Plamen Ratchevhttp://www.SQLStudio.com

Sorry, i did run it in Query analyser just did not put values in the
variables, oops

anyway when i did i got the message

UPDATE #b SET May2009 = (SELECT Total FROM #a
WHERE #a.[Pt No.] = #b.[Pt No.] and #a.daterange ="May 2009")

whcih indeed shows the double quotes and hence the invalid colomn but
I have not changed this SP for about a year and half and it always had
those double quotes.
The only explanation is that something was changed to make it act
differently with quoted identifiers etc in the live database - maybe a
recent service pack or something?? I dont know or am I just clutching
at straws I am just trying to find out if someone changed something in
the background without my knowledge. Anyway of finding out?

thank you
.

Relevant Pages