Jeff
2008-09-16 23:58:43 UTC
Hey
I get the incorrect syntax near keyword SET :(
This SP is created using Sql Server 2005 Enterprise, At my comp I don't have
that version of Sql Server. I use instead that FREE express vesion of Sql
Server 2005. The deal is that my boss created this SP on his machine and
then sent it to me... So I was wondering if for example there is a
difference in what is allowed to do in SP between Sql server 2005 enterprise
and the FREE express version. I mean the SP only have SELECTS, IF, CASE,
WHEN... I thought atleast that was allowed on the free vesion as well...
Here part of the SP, just in case you see something wrong with it... (the
last line I get that incorrect keyword at....)
@returparam nvarchar(25) OUT
DECLARE @str as nvarchar(25);
ELSE IF @filter IS NULL
SELECT CASE @tbl
WHEN N'normal' THEN (SELECT id, name, desc FROM Customer)
ELSE SET @returparam = @str;
Best Regards...
I get the incorrect syntax near keyword SET :(
This SP is created using Sql Server 2005 Enterprise, At my comp I don't have
that version of Sql Server. I use instead that FREE express vesion of Sql
Server 2005. The deal is that my boss created this SP on his machine and
then sent it to me... So I was wondering if for example there is a
difference in what is allowed to do in SP between Sql server 2005 enterprise
and the FREE express version. I mean the SP only have SELECTS, IF, CASE,
WHEN... I thought atleast that was allowed on the free vesion as well...
Here part of the SP, just in case you see something wrong with it... (the
last line I get that incorrect keyword at....)
@returparam nvarchar(25) OUT
DECLARE @str as nvarchar(25);
ELSE IF @filter IS NULL
SELECT CASE @tbl
WHEN N'normal' THEN (SELECT id, name, desc FROM Customer)
ELSE SET @returparam = @str;
Best Regards...