QOD 12/30
-
I thought I'd caught this one, that last comma before the ")" threw me. So, I pulled ups Qa and tried it -- sure 'nuff I got the warning but it ran...
Sneaky! 😉
Sloan
If you can't do it in SQL, get a bigger hammer!
Sloan
If you can't do it in SQL, get a bigger hammer! -
You're not alone Sloan. I was 100% absolutely positive that the comma was a syntax error.... until I did likewise - I got it wrong and then tried it myself.
Cheers,
- Mark
Cheers,
- Mark -
Oops, I didn't even notice the last comma!
Just adding the numbers and to me the answer was clear.
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url] -
I've run into this one before while developing with the exact same conditions, so it wasn't a suprise. That comma did look funny though 🙂
(And I can't believe this is the first time I've posted here... I've been reading the news letter, etc. forever...)
Edited by - bluefrog on 12/30/2003 02:35:44 AM
-
What 'last comma'???? This is the way it looked when I answered it.......
CREATE TABLE Employees (
EmployeeID nvarchar(10),
EmployeeName nvarchar(255),
EmployeeSocial nvarchar(255),
EmployeeStartDt datetime,
EmployeeReviewsMemo nvarchar(2040),
EmployeeNotes nvarchar(2040)
)
-SQLBill
-
Strange things happen these days
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url] -
I caught the error late last night and corrected it. My apologies. THe initial question had an additional column that I killed (but not the comma).
Brian Knight
http://www.sqlservercentral.com/columnists/bknight
Brian Knight
Free SQL Server Training Webinars -
The funny thing is that I executed the query with no warning...
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply