Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error Type!!!!

Status
Not open for further replies.

PhatH

IS-IT--Management
Mar 30, 2004
88
US
Hello all,

please tell me what this error means:

Error Type:
ADODB.Recordset (0x800A0CC1)
Item cannot be found in the collection corresponding to the requested name or ordinal.

I supposed this error meant the name I called was wrong or missing but I checked the database and it is there in a certain table and spelling is corrected.

Thanks
 
This is most common ADO error - field w/ specified name doesn't exist in result set.
Usually caused by typos, not SELECTed columns or missed aliases on columns.
Check SQL expression that fills Recordset, not table structure.
 
In the same time of calling this rs, I also called the rest of the table's recordsets. The rest of the recordsets was retrieved ok. Only this particular one giving me a headache. If I remove it out of the calling sequence, everything will be doing ok.

by the way, the data inside this recordset is states such as, CA,IL,FL,... it could be a single stateid or multiple.
again, no spelling error has occurred when calling the rs.

any idea??? ;-)
 
Check for leading/trailing spaces too.
IMO this problem likely isn't SQL2k-related, so another forum is better place to get answers.
Can you post source code there? Let me know if you want.
 
How will you be able to check which field is causing the error when the error comes up generally when trying to save/submit a web form though?

Louie C.
 
Does it containg a text or image column - if so move it to the last column of the recordset.

======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
 
ADO errors in VB can consist of more than one error. Set up some error trapping and when you get a VB error, also check for the ADO error. If there is one, then the error is ADO and you may need to step through an *array of errors* to read all the messages. You must display or capture these messages yourself because the environment only shows you the LAST one which can be the least descriptive.

I'm sorry I don't remember the name of the ADO error object off the top of my head. And, as someone suggested, you really should go post in the Access/VB forum. :)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top