PLEASE PLEASE HELP - How can I get a return value from a SQL Stored Proc is ASP.NET?

[jbonifacejr]

Hi. I'm sorry to bother all of you, but I have spent two days looking
at code samples all over the internet, and I can not get a single one
of them to work for me. I am simply trying to get a value returned to
the ASP from a stored procedure. The error I am getting is: Item can
not be found in the collection corresponding to the requested name or
ordinal.

Here is my Stored Procedure code.
set ANSI_NULLS ON
set QUOTED_IDENTIFI ER ON
Go
ALTER PROCEDURE [dbo].[sprocRetUPC]
@sUPC varchar(50),
@sRetUPC varchar(50) OUTPUT

AS

BEGIN
SET NOCOUNT ON;
SET @sRetUPC = (SELECT bcdDVD_Title FROM tblBarcodes WHERE bcdUPC =
@sUPC)
RETURN @sRetUPC

END
Here is my ASP.NET code.
Protected Sub Page_Load(ByVal sender As Object, ByVal e As
System.EventArg s) Handles Me.Load

Dim oConnSQL As ADODB.Connectio n

oConnSQL = New ADODB.Connectio n
oConnSQL.Connec tionString = "DSN=BarcodeSQL "
oConnSQL.Open()

Dim oSproc As ADODB.Command
oSproc = New ADODB.Command
oSproc.ActiveCo nnection = oConnSQL
oSproc.CommandT ype = ADODB.CommandTy peEnum.adCmdSto redProc
oSproc.CommandT ext = "sprocRetUP C"

Dim oParam1
Dim oParam2
oParam1 = oSproc.CreatePa rameter("sRetUP C",
ADODB.DataTypeE num.adVarChar,
ADODB.Parameter DirectionEnum.a dParamOutput, 50)
oParam2 = oSproc.CreatePa rameter("sUPC", ADODB.DataTypeE num.adVarChar,
ADODB.Parameter DirectionEnum.a dParamInput, 50, "0433960053 96")

Dim res
res = oSproc("sRetUPC ")

Response.Write( res.ToString())

End Sub

If I put the line -
oSproc.Execute( )

above the "Dim res" line, I end up with the following error:
Procedure or function 'sprocRetUPC' expects parameter '@sUPC', which
was not supplied. I thought that oParam2 was the parameter. I was also
under the assumption that the return parameter has to be declared
first. What am I doing wrong here?

[Gert-Jan Strik]

jbonifacejr wrote:

>
Hi. I'm sorry to bother all of you, but I have spent two days looking
at code samples all over the internet, and I can not get a single one
of them to work for me. I am simply trying to get a value returned to
the ASP from a stored procedure. The error I am getting is: Item can
not be found in the collection corresponding to the requested name or
ordinal.

Here is my Stored Procedure code.

set ANSI_NULLS ON
set QUOTED_IDENTIFI ER ON
Go
ALTER PROCEDURE [dbo].[sprocRetUPC]
@sUPC varchar(50),
@sRetUPC varchar(50) OUTPUT

AS

BEGIN
SET NOCOUNT ON;
SET @sRetUPC = (SELECT bcdDVD_Title FROM tblBarcodes WHERE bcdUPC =
@sUPC)
RETURN @sRetUPC

END

Here is my ASP.NET code.

Protected Sub Page_Load(ByVal sender As Object, ByVal e As
System.EventArg s) Handles Me.Load

Dim oConnSQL As ADODB.Connectio n

oConnSQL = New ADODB.Connectio n
oConnSQL.Connec tionString = "DSN=BarcodeSQL "
oConnSQL.Open()

Dim oSproc As ADODB.Command
oSproc = New ADODB.Command
oSproc.ActiveCo nnection = oConnSQL
oSproc.CommandT ype = ADODB.CommandTy peEnum.adCmdSto redProc
oSproc.CommandT ext = "sprocRetUP C"

Dim oParam1
Dim oParam2
oParam1 = oSproc.CreatePa rameter("sRetUP C",
ADODB.DataTypeE num.adVarChar,
ADODB.Parameter DirectionEnum.a dParamOutput, 50)
oParam2 = oSproc.CreatePa rameter("sUPC", ADODB.DataTypeE num.adVarChar,
ADODB.Parameter DirectionEnum.a dParamInput, 50, "0433960053 96")

Dim res
res = oSproc("sRetUPC ")

Response.Write( res.ToString())

End Sub

If I put the line -
oSproc.Execute( )

above the "Dim res" line, I end up with the following error:
Procedure or function 'sprocRetUPC' expects parameter '@sUPC', which
was not supplied. I thought that oParam2 was the parameter. I was also
under the assumption that the return parameter has to be declared
first. What am I doing wrong here?

Just a few pointers here:
- creating a parameter will just create a parameter. To use it, you need
to add it to the command object using oSProc.Paramete rs.Append
- in a stored procedure you can only use the RETURN keyword to return an
integer, so @sRetUPC is out of the question
- if you want to use the value of the output parameter, then you should
access it through the Parameters collection of the Command object. The
syntax you are currently using refers to the resultset, but the stored
procedure does not have one

HTH,
Gert-Jan

[jbonifacejr]

Thank you for your help. Any chance you have a moment to help just a
little more? Here is what I did, but I still can't access the value
output by the stored proc...

I removed the Return @sRetUPC line. I am guessing that I can rely on
the set @sRetUPC line to set the value of the output parameter

>From there, I appended the parameters in the ASP code...like this

oSproc.Paramete rs.Append(oPara m2)
oSproc.Paramete rs.Append(oPara m1)
--originally I tried to do Param1 then Param2, but I got an error
about the parameter
--type being an output, so I just figured I had them in the wrong
order because the
--first parameter in the code was the output one.

Then, I added the line oSproc.Execute( )
After that is:
Dim res
res = oSproc.Paramete rs.Item("sRetUP C").Value.toStr ing()

This is not working. Do you know how I can get access to the value of
the parameter that is returned?

Just a few pointers here:
- creating a parameter will just create a parameter. To use it, you need
to add it to the command object using oSProc.Paramete rs.Append
- in a stored procedure you can only use the RETURN keyword to return an
integer, so @sRetUPC is out of the question
- if you want to use the value of the output parameter, then you should
access it through the Parameters collection of the Command object. The
syntax you are currently using refers to the resultset, but the stored
procedure does not have one

HTH,
Gert-Jan

[Erland Sommarskog]

jbonifacejr (jb*********@ho tmail.com) writes:

Thank you for your help. Any chance you have a moment to help just a
little more? Here is what I did, but I still can't access the value
output by the stored proc...

I removed the Return @sRetUPC line. I am guessing that I can rely on
the set @sRetUPC line to set the value of the output parameter

>>From there, I appended the parameters in the ASP code...like this

oSproc.Paramete rs.Append(oPara m2)
oSproc.Paramete rs.Append(oPara m1)
--originally I tried to do Param1 then Param2, but I got an error
about the parameter
--type being an output, so I just figured I had them in the wrong
order because the
--first parameter in the code was the output one.

Then, I added the line oSproc.Execute( )
After that is:
Dim res
res = oSproc.Paramete rs.Item("sRetUP C").Value.toStr ing()

This is not working. Do you know how I can get access to the value of
the parameter that is returned?

Never say "not working" in newsgroup post with explaining what it
means. Do you get an unexpected result? An error message? Something
else?

Since I don't even know how your code looks like right now, just two
notes:

1) Use parameter names with leading @. The underlying provider may
prefer that.

2) Use adParamInputOut put for the output value. T-SQL does not have any
true output-only parameters. (Save the return value, but there is a
separate enum value for return values as I recall.)
--
Erland Sommarskog, SQL Server MVP, es****@sommarsk og.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

[jbonifacejr]

If you look at the top post you will see where I put the code I am
using. I also tried to let people know what happened when I tried their
suggestions. But, thanks for the advice...and I'll look at those SQL
Books online.

Jan

Erland Sommarskog wrote:

jbonifacejr (jb*********@ho tmail.com) writes:

Thank you for your help. Any chance you have a moment to help just a
little more? Here is what I did, but I still can't access the value
output by the stored proc...

I removed the Return @sRetUPC line. I am guessing that I can rely on
the set @sRetUPC line to set the value of the output parameter

>From there, I appended the parameters in the ASP code...like this

oSproc.Paramete rs.Append(oPara m2)
oSproc.Paramete rs.Append(oPara m1)
--originally I tried to do Param1 then Param2, but I got an error
about the parameter
--type being an output, so I just figured I had them in the wrong
order because the
--first parameter in the code was the output one.

Then, I added the line oSproc.Execute( )
After that is:
Dim res
res = oSproc.Paramete rs.Item("sRetUP C").Value.toStr ing()

This is not working. Do you know how I can get access to the value of
the parameter that is returned?

Never say "not working" in newsgroup post with explaining what it
means. Do you get an unexpected result? An error message? Something
else?

Since I don't even know how your code looks like right now, just two
notes:

1) Use parameter names with leading @. The underlying provider may
prefer that.

2) Use adParamInputOut put for the output value. T-SQL does not have any
true output-only parameters. (Save the return value, but there is a
separate enum value for return values as I recall.)
--
Erland Sommarskog, SQL Server MVP, es****@sommarsk og.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

[othellomy]

Why are you using stored proc when you can use a function(s)? I always
thought the output parameter was a bit of a hack and clumsy to use.

jbonifacejr wrote:

If you look at the top post you will see where I put the code I am
using. I also tried to let people know what happened when I tried their
suggestions. But, thanks for the advice...and I'll look at those SQL
Books online.

Jan

Erland Sommarskog wrote:

jbonifacejr (jb*********@ho tmail.com) writes:

Thank you for your help. Any chance you have a moment to help just a
little more? Here is what I did, but I still can't access the value
output by the stored proc...
>
I removed the Return @sRetUPC line. I am guessing that I can rely on
the set @sRetUPC line to set the value of the output parameter
>
>>From there, I appended the parameters in the ASP code...like this
oSproc.Paramete rs.Append(oPara m2)
oSproc.Paramete rs.Append(oPara m1)
--originally I tried to do Param1 then Param2, but I got an error
about the parameter
--type being an output, so I just figured I had them in the wrong
order because the
--first parameter in the code was the output one.
>
Then, I added the line oSproc.Execute( )
After that is:
Dim res
res = oSproc.Paramete rs.Item("sRetUP C").Value.toStr ing()
>
This is not working. Do you know how I can get access to the value of
the parameter that is returned?

Never say "not working" in newsgroup post with explaining what it
means. Do you get an unexpected result? An error message? Something
else?

Since I don't even know how your code looks like right now, just two
notes:

1) Use parameter names with leading @. The underlying provider may
prefer that.

2) Use adParamInputOut put for the output value. T-SQL does not have any
true output-only parameters. (Save the return value, but there is a
separate enum value for return values as I recall.)
--
Erland Sommarskog, SQL Server MVP, es****@sommarsk og.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

[Erland Sommarskog]

jbonifacejr (jb*********@ho tmail.com) writes:

If you look at the top post you will see where I put the code I am
using.

Since then you changed the code according to Gert-Jan's advice, and we
don't know what it looked after that.

Basically, if you only say "not working" without specifying why, and
don't show us the code, don't expect that much help. But that's your call.

--
Erland Sommarskog, SQL Server MVP, es****@sommarsk og.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

[jbonifacejr]

Thanks Erland...I see where I screwed up. I thought I had explained
what was wrong, but I did that in a different thread in another forum.

Anyway, I got this working using classic ASP and ADODB. Now I am going
to try to get it working over ASP.NET and ADO.NET. Wish me luck.

So far, eveerything works except that I am constantly being told that
the stored procedure expects a parameter that was not supplied.
However, The same two parameters are created and added to the
Parameters of the command object.

I'll continue to work on it and see if I can get it to work. Looks like
I need a datareader or some other object. I found a great KB article
that basically shows me everythig I am doing (right and wrong)...

http://support.microsoft.com/kb/306574
Erland Sommarskog wrote:

jbonifacejr (jb*********@ho tmail.com) writes:

If you look at the top post you will see where I put the code I am
using.

Since then you changed the code according to Gert-Jan's advice, and we
don't know what it looked after that.

Basically, if you only say "not working" without specifying why, and
don't show us the code, don't expect that much help. But that's your call.

--
Erland Sommarskog, SQL Server MVP, es****@sommarsk og.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

[Erland Sommarskog]

jbonifacejr (jb*********@ho tmail.com) writes:

Thanks Erland...I see where I screwed up. I thought I had explained
what was wrong, but I did that in a different thread in another forum.

Posting the same question independently to two forums is not a nice
thing to. This means that people can waste time on answering your post,
when it has already been answered elsewhere.

Anyway, I got this working using classic ASP and ADODB. Now I am going
to try to get it working over ASP.NET and ADO.NET. Wish me luck.

So far, eveerything works except that I am constantly being told that
the stored procedure expects a parameter that was not supplied.
However, The same two parameters are created and added to the
Parameters of the command object.

Again, without seeing your code it's hard to tell. There is a difference
between ADO and SqlClient though: with ADO, the parameter names are
just local to the application, so if you misspell a parameter name,
you may get away with it. Not so with SqlClient.

I'll continue to work on it and see if I can get it to work. Looks like
I need a datareader or some other object.

Since your procedure has an output parameter, but no result set, the most
conventient method to use is ExecuteNonQuery , in which case you only need
the Command object.
--
Erland Sommarskog, SQL Server MVP, es****@sommarsk og.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx