Help with Error Message

[Dynapen]

I am running a ASP JavaScript App against a Oracle 8i DB.

When building my SQL statement in the page, to pass to Oracle using the bind varialbes and the parameters object, I get the following error.

Provider error '80040e55'

Column does not exist.


I know that the values are correct in my parameters. I know the parameter types are correct. And i know that the sql statement is valid becuase i can Response.Write(commobj.Commandtext) and then copy and paste that into SQL Plus and the code works fine.

But MS doesn't have anything on this error, so i am hoping that at least one of you has seen this and can help me out before I am tempte to throw my computer across the office.

Help Please. The money's gone, the brain is shot.....but the liquor we still got.

 

[snowboardr]

Code would help. jason@vzio.com

http://www.vzio.com/images/banners/s_vzio.gif

 

[Dynapen]

Can't really post the code to this one. Normally I would have, but this is a weird deal where I really can't. Mainly I am looking for someone who has dealt with this error before, when trying to run SQL statements.

Here is the object references that are opening the SQL statements (it's just the SQL that I can't post)




connobj=Server.CreateObject("adodb.connection"
commobj=Server.CreateObject("adodb.command"

connobj.Open(ODSEProvider);
commobj.ActiveConnection = connobj;

rsobj=Server.CreateObject("adodb.recordset"
rsobj.CursorLocation = adUseClient;
rsobj.CursorType = adOpenStatic;

commobj.Parameters.Append(commobj.CreateParameter("PMOS", adVarChar, adParamInput, 4, PMOS));
commobj.Parameters.Append(commobj.CreateParameter("grade", adNumeric, adParamInput, 2, grade));
commobj.CommandText=jrsql;

Response.Write (commobj.CommandText);

rsobj.Open(commobj);

I get the error from the line that has the Open command, which tells me that it isn't a problem in IIS parsing the code, but in this case in the provider when it tries to execute the statement against the DB. Again, I can print the SQL statement to the screen, apply specific values to the parameterized fields, and the code runs fine in SQL Plus for Oracle 8i. I am using these same object references in most of my pages, and they work fine everywhere else.

Does anyone have any ideas, or a site to research the error code (what I really want) The money's gone, the brain is shot.....but the liquor we still got.

 

[Dynapen]

Figured this one out. It was caused by a parameter getting created at the top of the page, used once, and then not destroyed. So the Command object was seeing it as a valid parameter still. That gave me 2 parameter prompts in the SQL, but 3 parameters. They didn't match up, so the provider threw that error. The money's gone, the brain is shot.....but the liquor we still got.