I'm calling an Oracle 10g stored procedure from an ASP file across an
ODBC connection using the Oracle (ASP code is listed below, assume
that all arguments are of correct type and value). I get the following
error:

Microsoft OLE DB Provider for ODBC Drivers error '80040e21'
ODBC driver does not support the requested properties.
/atx/SPTEST.ASP, line 41

Line 41 is cmd.Execute

Can anyone please shed some light on this problem? It's vexing my
soul!

Thanks!
- Jeff

Public Function UpdateFlagByKey(cn, lngKey, strField, varValue)
' Update a specific flag for a key
Dim strErr
Dim strValue
Dim cmd

set cmd = server.createobject("ADODB.Command")

' convert the variant to string
strValue = CStr(varValue)

' set the command object and command type
cmd.ActiveConnection = cn

cmd.CommandType = adCmdStoredProc

' assign stored procedure
cmd.CommandText = "ATXAMBsReading.UpdateFlagByKey"

' assign input parameters
cmd.Parameters.Append cmd.CreateParameter("myKey", adNumeric,
adParamInput, lngKey)
cmd.Parameters.Append cmd.CreateParameter("myField", adChar,
adParamInput, 50, strField)
cmd.Parameters.Append cmd.CreateParameter("myValue", adChar,
adParamInput, 50, strValue)

' execute the stored procedure
cmd.Execute

End Function

9/1/2004 9:27:25 AM

Jeff <jpaar (AT) envirosys (DOT) com> wrote in message

<91279873.0409010527.3209c731 (AT) posting (DOT) google.com>





Jeff,

The error "Microsoft OLE DB Provider for ODBC Drivers error
'80040e21' ODBC driver does not support the requested properties."
implies that the underlying ODBC Driver doesn't implement ODBC
functionality that is required by the Microsoft OLE DB to ODBC Bridge.


Here are your options as I see them:

1. Obtain / evaluate an alternative OLE DB to ODBC Bridge as the one
from Microsoft isn't your only option. The benefit here being that
you will not need to change or reconfigure your underlying ODBC
Driver and DSN combination.

An alternative OLE DB to ODBC Bridge is available at: http://uda.
openlinksw.com/oledb/st/oledb-odbc-st/ (it makes far more ODBC
Drivers usable via OLE DB clients than the one from Microsoft).

2. Obtain / evaluate an alternative ODBC Driver for Oracle (one that
implements the functionality required by the OLE DB to ODBC Bridge).

An allternative ODBC Driver for Oracle is available at:

http://uda.openlinksw.com/odbc/st/odbc-oracle-st/ (Single-Tier -
requires SQL*Net or Net8+)

or

http://uda.openlinksw.com/odbc/mt/odbc-oracle-mt/ (Multi-Tier -
doesn't require SQL*Net or Net8+ and provides enhanced enterprise
level security etc..)

To totally understand the vagueries of what is going on here you need
an ODBC diagnostic utility that can show you what calls are being
made by the ODBC Client (in this case the OLE DB to ODBC Bridge) and
where they fail in the underlying Driver.

OpenLink ODBC Scan will unveil what is happening here, along the
lines presented above. You can download this utility from:
http://oplweb.openlinksw.com:8080/download/util.vsp



Regards,



Kingsley Idehen Weblog: http://www.openlinksw.com/blog/~kidehen

OpenLink Software Web: http://www.openlinksw.com

Universal Data Access & Universal Integration Middleware Providers.

Thanks for the assistance!

- Jeff