Arguments are of the wrong type, are out of acceptable range, or are in conflict with

[msfdisk]

HI I'm getting this wonderful error: ADODB.Command error '800a0bb9'

Arguments are of the wrong type, are out of acceptable range, or are in conflict with one another.

Here is my Stored Proc call:

'-----------------------------------------------------------------------------------'
'
intFormID = "145"
strDDName = "DrugSideEffectEducation"
Response.Write "<br><br><br>" &intFormID

Set objSelectCommand = Server.CreateObject("ADODB.Command")
Set objConn = Server.CreateObject("ADODB.Connection")
Set objSelectEduRS = Server.CreateObject("ADODB.Recordset")
objSelectCommand.CommandType = adCmdStoredProc
With objSelectCommand
' .CommandType = adCmdStoredProc
.CommandText = "usp_FetchDropDownSelections"
' .Parameters.Append .CreateParameter("@FormID", adInteger, adParamInput, ,intFormID)
.Parameters.Append .CreateParameter("@DDName", adVarChar, adParamInput, 150, strDDName)
.Execute
.WriteParams
End With
objSelectEduRS.Open objConn,,adOpenStatic, adLockOptimistic

'-----------------------------------------------------------------------------------

[ngaisteve1]

Did you set DDName to varchar(150) at your usp_FetchDropDownSelections?

[msfdisk]

yes: Here is the stored Proc-----



set ANSI_NULLS ON
set QUOTED_IDENTIFIER ON
GO
-- =============================================
-- Author: <Author,,Name>
-- Create date: <Create Date,,>
-- Description: <Description,,>
-- =============================================
ALTER PROCEDURE [dbo].[FetchDropDownSelections]
-- Add the parameters for the stored procedure here
@FormID int = 0,
@DDName varchar(150)
AS
BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;

-- Insert statements for procedure here
SELECT *
FROM dbo.DropDownEditor
WHERE FormID = @FormID
And DDName = @DDName
And Active = 1

END

[Wolffy]

' .Parameters.Append .CreateParameter("@FormID", adInteger, adParamInput, ,intFormID)

Is this line commented out when you get the error, or was that part of trying to debug it?