Microsoft KB Archive/174638

From BetaArchive Wiki

Article ID: 174638

Article Last Modified on 5/2/2006


  • Microsoft Visual InterDev 1.0 Standard Edition
  • Microsoft Data Access Components 2.5
  • Microsoft Data Access Components 2.6
  • Microsoft Active Server Pages 4.0

This article was previously published under Q174638


One of the following errors occurs when passing a date to a SQL Stored Procedure:

Microsoft OLE DB Provider for ODBC Drivers error 80004005 At least one parameter contained a type that was not supported.


Microsoft OLE DB Provider for ODBC Drivers error 80040e21 Driver not capable.


The data type of the parameter being passed to the stored procedure does not match the data type the stored procedure is expecting. For example, passing a value of "7/21/97" to a stored procedure that is expecting DateTime data will cause the error.


Make sure the data type you are passing to the stored procedure is of the same type as the stored procedure is expecting. Using Visual InterDev's Data Command control to create the Active Server Pages (ASP) code to call your stored procedure will ensure the parameter is of the correct type.


This behavior is by design.


Steps to Reproduce Behavior

  1. Create or open a Visual InterDev project.
  2. Add a data connection to the "Pubs" database on your SQL server.
  3. From the Data View tab, right-click the Stored Procedures folder for the "Pubs" database and choose "New Stored Procedure" from the context menu.
  4. Copy/paste the code between the "===" lines below into the new stored procedure.

          ========new stored procedure code==========
          CREATE PROCEDURE sp_custom_sel
             @custdate datetime
          SELECT *
             FROM employee
             WHERE employee.hire_date=@custdate
  5. Create a new ASP file in the project.
  6. Copy/paste the code below

          ======ASP file to call stored procedure===================
          <%@ LANGUAGE="VBSCRIPT" %>
          <META NAME="GENERATOR" Content="Microsoft Visual InterDev 1.0">
          <META HTTP-EQUIV="Content-Type" content="text/html;
          <TITLE>Document Title</TITLE>
          Set pubs = Server.CreateObject("ADODB.Connection")
          pubs.ConnectionTimeout = Session("pubs_ConnectionTimeout")
          pubs.CommandTimeout = Session("pubs_CommandTimeout")
          pubs.Open Session("pubs_ConnectionString"),
          Session("pubs_RuntimeUserName"), Session("pubs_RuntimePassword")
          Set cmdTemp = Server.CreateObject("ADODB.Command")
          Set DataCommand1 = Server.CreateObject("ADODB.Recordset")
          cmdTemp.CommandText = "dbo.""sp_custom_sel"""
          cmdTemp.CommandType = 4
          Set cmdTemp.ActiveConnection = pubs
          Set tmpParam = cmdTemp.CreateParameter("Return Value", 3, 4, 4)
          cmdTemp.Parameters.Append tmpParam
          'The 7 in the "CreateParamter" below defines the passed value
          '-"7/18/61"-as a Date data type.  Changing the 7 to 135 defines the
          'passed value as a Datetime data type, which the stored procedure is
          'expecting. For more information on data type values, see the "Type
          'Property" topic in InfoView.
          Set tmpParam = cmdTemp.CreateParameter("@custdate",
            7, 1, 16,"7/18/97")
          cmdTemp.Parameters.Append tmpParam
          'DataCommand1.Open cmdTemp, , 0, 1
  7. Preview the ASP page. The error described in the SYMPTOMS section above will appear.
  8. Change the 7 in the "CreateParameter" line of the ASP to 135. Save and run the ASP page. No error will appear.


For the latest Knowledge Base articles and other support information on Visual InterDev and Active Server Pages, see the following page on the Microsoft Technical Support site:

Keywords: kbstoredproc kbvisid600fix kbprb KB174638