ADO error

[tmcneil]

Hi All,

I've got this line in a call to an oracle stored procedure that I just can't seem to fix.

set param = comm.CreateParameter("TakeID",				adInteger, adParamInput, ,	    TakeID)

It used to be ok until I changed the values being sent to it. it used to be no higher than 59999, now it's over 70000. I know that this is the problem, however, here is the error:

Error Type:
Provider (0x8002000A)
Out of present range.
/mbtapacis/include/message.asp, line 199

I've tried chnaging the adInteger to an adBigInt, which makes perfect sense.

set param = comm.CreateParameter("TakeID",				adBigInt, adParamInput, ,	    TakeID)

This is the result...

Error Type:
ADODB.Parameters (0x800A0E7C)
Parameter object is improperly defined. Inconsistent or incomplete information was provided.
/mbtapacis/include/message.asp, line 200

Not sure if this is progress or not.....

So, I basically need to find something that can handle numbers around 70000 range.

Thanks,
Todd

 

[monksnake]

This leaves me with adNumeric

Have you tried by any chance pulling the parameter in as adNumeric, then grabbing it in the Oracle DB as Decimal??



<.

 

[tmcneil]

Yes, but again, it's not working. It's in the definition of the CreateParameter. I've tried adDouble also. I'm pretty much at a loss.....

 

[PHV]

Are you sure your ODBC driver is up to date for you version of Oravle ?

 

[tmcneil]

I have oracle 9.2.0.4 with oracle odbc driver 9.02.00.06. I think it is up to date. The strange thing is that we are handling some id's into the 100K number range via C++ interfacing with oracle. So, I'm not sure what I am doing wrong as I think I am following the guidelines.

 

[tmcneil]

All,

I had someone else take a fresh look at it as I could not see the forest from the trees (so to speak) and it was found that two values were not being set prior to the call to the stored procedure and caused the ado error. it had nothing to do with the value being above 65535. So, I appreciate everyone's reponse and patience, but I believe it is taken care of now.

Thanks,