February 26, 2004 at 7:15 pm
You have to name your parameter or it will assume it the first parameter is being entered.
Conn.Execute("search_orders_1 @xGroup_Name = '" & request.form("Group_Name") & "'")
February 26, 2004 at 7:36 pm
besides the above correction I believe that to use the connection object to execute the procedure is not the best way I would recommend you use the command object instead
* Noel
February 27, 2004 at 2:09 am
No problem!
Although it does seem so, I'm not totally against the use of dynamic sql. There are cases with very complex searches where you are better off with dynamic sql, but these are few.
![]()
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
February 27, 2004 at 4:30 am
I am wondering if the SP works at all with the syntax that it is written with currently , I believe the variables should not be included inside the apostophies like it should be
IF @id IS NOT NULL
SELECT @sql = @sql + ' AND d.id = @xid'
should be
IF @id IS NOT NULL
SELECT @sql=@sql+ ' AND d.id ='+ ''+ @xid + ''
Otherwise the variables may not get substituted with the passed in values as even the variable will be considered as part of the string, and if the variable is of int or numeric type then it can be written as
SELECT @sql=@sql+ ' AND d.id ='+ @xid
I don't know if I am missing anything here.
Thanks
Prasad Bhogadi
www.inforaise.com
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply