Classic ASP - "ORA-01722: invalid number" using OraOLEDB.Oracle driver

Question

I am working on doing some maintenance updates to a Classic ASP website, and I need to be able to run an insert/update statement for putting values into a lookup table. I am currently running into an "ORA-01722: invalid number" error when trying to use ADO and bind variables for my insert statement.
Below is an example of a table that I am having problems with:
CREATE TABLE "MATMGR"."TEST_SWING_TABLE"
(     "TABLE1_ID" NUMBER(4,0) NOT NULL ENABLE,
     "TABLE2_ID" NUMBER(4,0) NOT NULL ENABLE,
     CONSTRAINT "TEST_SWING_TABLE_PK" PRIMARY KEY ("TABLE1_ID", "TABLE2_ID")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS" ENABLE
) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS" ;
Here is some snippet code of the basic functionality I am trying to get to work:
''START CODE''
Dim connDb, cmdDoseInsert
Set connDb = Server.CreateObject("ADODB.Connection")
connDb.CursorLocation = adUseClient ' Setup to return RecordSet
connDb.ConnectionString = "Provider=OraOLEDB.Oracle;Data Source={host};User ID={user id};Password={password}"
connDb.Open()
Set cmdDoseInsert = Server.CreateObject("ADODB.command")
Set cmdDoseInsert.ActiveConnection = connDb
cmdDoseInsert.CommandType = adCmdText
cmdDoseInsert.NamedParameters = true ' Set the command object to use named parameters
cmdDoseInsert.Prepared = true
cmdDoseInsert.CommandTimeout = 0
cmdDoseInsert.CommandText = "INSERT INTO TEST_SWING_TABLE (TABLE1_ID, TABLE2_ID) VALUES (:P_TABLE1_ID, :P_TABLE2_ID)"
cmdDoseInsert.Prepared = true
cmdDoseInsert.Parameters.Append cmdDoseInsert.CreateParameter("P_TABLE1_ID", adNumeric, adParamInput)
cmdDoseInsert.Parameters.Append cmdDoseInsert.CreateParameter("P_TABLE2_ID", adNumeric, adParamInput)
'... START: While Looping
     cmdDoseInsert.Parameters(0).Value = {some numeric value}
     cmdDoseInsert.Parameters(1).Value = {some numeric value}
     cmdDoseInsert.Execute
'... END: Looping
''END CODE''
What I have been able to find out so far is that there is some type of issue with numeric values getting translated right when sending two and retrieving from Oracle in ASP. So, does anyone have any thoughts on how to resolve this as I would like to use parameterized SQL to improve application performance?
I am connecting to a developmental server running Oracle 9.2

Answer 1

Ok, in my slightly larger example I found out that for what ever reason my named parameters are not being enforced, and so I had to make sure that the parameters were in the same order as they appeared in the SQL. To be on the save side, I did this when they were added as well as when I was assigning values to them.
Can anyone tell me if this is an Oracle issue or a ASP issue?