80040e21 - BUG - Solution/Work-Around!!!!

Joe Condomina

unread,

Mar 21, 1998, 3:00:00 AM3/21/98

to

Solution to:

80040e21... Errors Occurred.

Anyhow after two days of wrestling with this, I found out something which
solved my problem.

This error seems to occur when you are referencing fields in a SQL Database
that are of type TEXT. What I found was that you must reference/retrieve
the text data from you ASP code in the same order as you have it in your dB.

For Example:

The dB is defined as:
col1 text 16
col2 text 16
col3 char 10
col4 text 16
col5 text 16

Your asp MUST pull the TEXT values in the order that they appear in the dB:
rs.Fields("col1").Value
rs.Fields("col2").Value
rs.Fields("col4").Value
rs.Fields("col5").Value

If you do the following it will generate the error:
rs.Fields("col1").Value
rs.Fields("col2").Value
rs.Fields("col5").Value
rs.Fields("col4").Value

Believe it or not, it was the root of my problems. I think that it might be
associated to the way that SQL Server retrieves the TEXT type fields with
the record set. It might actually keep pointers to bytes of data within a
TEXT field in the dB when you are pulling it, so if you access them out of
order the pointer gets corrupted and you cannot access anything else. I
think this might also be the case in MS Access memo fields. I have not
tried this theory in Access. I will have to see.

So if you are getting any weird errors like 80020009 or 80040e21 make sure
the above is not happening.

Ton

unread,

Mar 21, 1998, 3:00:00 AM3/21/98

to

thanks for sharing

Ton

Joe Condomina heeft geschreven in bericht
<385140BE6BFEB4A8.D216A94F...@library-proxy.airnews.ne
t>...

John Fenderson

unread,

Mar 23, 1998, 3:00:00 AM3/23/98

to

I've seen alot of posts about people needing FTP/Email etc. components, take
a look at http://www.xde.net/quickaspobjects We were part of the beta test
program and have been addicted to them ever since!

John Fenderson
Senior Developer
Web Cookers

Arjan Steenbergen

unread,

Mar 24, 1998, 3:00:00 AM3/24/98

to

Hi,

You are totally right. I found it out too. I was just about to post the
message when I saw yours.
There is another workaround: name the fields that you are using on the page
in exactly the same order in the SELECT statement, so:

SELECT col2, col1 FROM ...

and then use

Hi <%=rs("col2")%> from <%=rs("col1")%>

Greetings,
Arjan Steenbergen

Joe Condomina wrote in message

Graham Walmsley

unread,

Mar 31, 1998, 3:00:00 AM3/31/98

to

I have also seen exactly the same problem, but it took me 3 days to work it
out! I still have a problem calling the same stored procedure twice though.
Back to the drawing board.

Regards

Graham

Vincent Armato

unread,

Apr 11, 1998, 3:00:00 AM4/11/98

to

We are experienced this error when we push a simple two table join through
ASP down to Oracle 7.3 using ADO 1.5 with MS Oracle ODBC Driver:

Microsoft OLE DB Provider for ODBC Drivers error '80040e21'
The request properties can not be supported by this ODBC Driver.

Any ideas? Only some sql statements fail while others work. We can't seem
to find a pattern. If we take the exact same SQL and push it through Oracle
Objects for OLE or SQLPlus it works fine. It appears that ADO/ODBC is the
bottleneck to the problem.

Any ideas?

- Vince Armato

Graham Walmsley wrote in message ...