FIX: Using ODBCDirect, Transactions and Oracle Causes Hang (172313)
The information in this article applies to:
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
This article was previously published under Q172313 SYMPTOMS
When connecting to an Oracle database using DAO and ODBCDirect, the
application hangs when an Insert statement is within a Begin/Commit
Transaction and that procedure is called the second time.
CAUSE
This is caused by a known problem in the Microsoft ODBC Driver for Oracle,
Msorcl10.dll, version 1.0.
RESOLUTION
To work around this problem the QueryTimeout property of the Connection
object must be set to zero (0). Uncomment the following line of code to
make the example run without error:
Cn.QueryTimeout = 0
STATUS
Microsoft has confirmed this to be a problem in the Microsoft ODBC Driver
for Oracle, Msorcl10.dll. This issue has been resolved with the 2.0, or
higher, version of the Microsoft Oracle ODBC Driver. This driver can be
obtained in Visual Studio 5.0 and higher, MDAC 1.5 or higher, and the Data
Access Software Development Kit (SDK).
Modification Type: | Minor | Last Reviewed: | 3/2/2005 |
---|
Keywords: | kbbug kbDriver kbDSupport kbMDACNoSweep kbODBC200fix kbOracle KB172313 |
---|
|