Re: Adding date to parameter

You were right on the mark. Originally the code has @index as parameter(2),
which was ok when the date didn't exist. I changed the order of the
parameters so that @ClaimedDate was paramter(2) and @index was parameter(3).
I made the assumption that the stored procedure went by the @paramtername not
the order.

Thank you for that insight!


"W.G. Ryan [MVP]" wrote:

Check your indexes. 0 is the first param, so 3 maps to the @index variable
which is an int. I think this is your issue, but if not, let me know.
"T McDonald" <TMcDonald@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DF708DCB-FDE9-4742-B3F2-67DC356876FD@xxxxxxxxxxxxxxxx
I'm having a problem inserting a date into a SQL server database using a
parameter. I keep getting the following error:

"Implicit conversion from data type datetime to int is not allowed. Use
the
CONVERT function to run this query."

ClaimedDate is declared as a String. When I run through the debugger,
ClaimedDate does appear to have a properly formatted date.

Parameters(3) = New Data.OleDb.OleDbParameter
Parameters(3).ParameterName = "@WhenClaimed"
Parameters(3).OleDbType = OleDbType.Date

I've tried adding the value with both of the following with no success:
Parameters(3).Value = DateTime.Parse(ClaimedDate)
Parameters(3).Value = CDate(ClaimedDate)

I am using the following stored procedure:

ALTER PROCEDURE [dbo].[spUpdateClaimedBy]
-- Add the parameters for the stored procedure here
@ClaimedBy varchar(50) = 0,
@ClaimedByName varchar(250) = 0,
@WhenClaimed datetime = date,
@Index int = 0
AS
BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;

-- Insert statements for procedure here
UPDATE dbo.Accounts
SET ClaimedBy = @ClaimedBy, ClaimedByName = @ClaimedByName, WhenClaimed =
@WhenClaimed
WHERE [Index] = @Index
END

Any help would be greatly appreciated.



.

Relevant Pages

  • Re: Adding date to parameter
    ... ClaimedDate does appear to have a properly formatted date. ... I am using the following stored procedure: ... -- SET NOCOUNT ON added to prevent extra result sets from ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Adding date to parameter
    ... and SqlClient with dates, but I don't think I could rewrite the code in a ... I am using the following stored procedure: ... -- SET NOCOUNT ON added to prevent extra result sets from ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Adding date to parameter
    ... I made the assumption that the stored procedure went by the @paramtername ... "Implicit conversion from data type datetime to int is not allowed. ... -- SET NOCOUNT ON added to prevent extra result sets from ...
    (microsoft.public.dotnet.framework.adonet)
  • RE: What stored procedures call this stored procedure?
    ... this in the wrong way - I have the ID of a stored procedure and I'm looking ... > set nocount on ... > declare @rv int ...
    (microsoft.public.sqlserver.programming)
  • Re: Adding date to parameter
    ... "Implicit conversion from data type datetime to int is not allowed. ... I am using the following stored procedure: ... -- SET NOCOUNT ON added to prevent extra result sets from ...
    (microsoft.public.dotnet.framework.adonet)
Loading