[Resolved] Return value of Stored Procedure

[naruponk]

"Arithmetic overflow converting expression to data type smalldatetime"

I'm using a code which i posted really.

Parameters.Append .CreateParameter("RETURN", adInteger, adParamReturnValue)

Is return value should be 1st parameter?

[naruponk]

I have create new stored proc which is requires 1 parameter only (@A)

.Parameters.Append .CreateParameter("@A", adBigInt, adParamInput, , 1)
.Parameters.Append .CreateParameter("@Result", adBigInt, adParamReturnValue)

above code will give me that ""Stored Proc ... has too many agrument specific"

.Parameters.Append .CreateParameter("@Result", adBigInt, adParamReturnValue)

This will give me that " ... @A not supplied"
Am i giving incorrect format?

[szlamany]

I'm pretty sure that the RETURN {int} T-SQL command does not return that value in the PARAMETER collection.

I cannot find backup for this in MSDN - I've got a good ADO book at work that I'll check in 30 minutes...

Why are you so stuck on using RETURN {int} and not simply creating a list of INPUT and OUTPUT parameters? My example showed how to do that quite easily.

The error you keep saying you are getting sounds more like a VB/ADO side error - that the object is not properly created and the SPROC isn't even executing.

BTW - we decided at the start of our development project in VB/ADO/SQL that using LONG (VB) and INT (SQL) was the only integer style we would support. DATETIME also - no small datetime. Supporting lots of different datatypes in the PARAMETER logic is too complex.

[PilgrimPete]

I'm pretty sure that the RETURN {int} T-SQL command does not return that value in the PARAMETER collection.

I cannot find backup for this in MSDN - I've got a good ADO book at work that I'll check in 30 minutes...

Why are you so stuck on using RETURN {int} and not simply creating a list of INPUT and OUTPUT parameters? My example showed how to do that quite easily.

The error you keep saying you are getting sounds more like a VB/ADO side error - that the object is not properly created and the SPROC isn't even executing.

BTW - we decided at the start of our development project in VB/ADO/SQL that using LONG (VB) and INT (SQL) was the only integer style we would support. DATETIME also - no small datetime. Supporting lots of different datatypes in the PARAMETER logic is too complex.

I agree with the OUTPUT parameters idea szlamany - sorry missed that bit in your previous post when I posted this:

...though I generally lean towards using an output parameter to return data values, and save the adParamReturnValue parameter to return the success (or otherwise) of my proc...

naruponk - the adParamReturnValue parameter has to be the first you add to the parameters collection in the VB code, otherwise you will get the error you report.

[naruponk]

Ok .... look works
Thanks for ideas & helps guys