Oracle ODBC driver: connection is part of COM+ transaction, then starts new transaction after error

[PaulB]

I am using the Oracle ODBC driver (version 10.02.00.03) on
Windows 2003 SP2 in a COM+ object that Supports transactions.
A COM+ transaction has started, and I call SQLConnect to create
a connection. The transaction is long-running. I use the connection
until the MSDTC timeout expires. At that point, I get an Oracle
error "ORA-24761: transaction rolled back" which is what I expect.

However, this is a very large legacy application and it ignores the
Oracle error and keeps on using the same ODBC connection.
I hope/expect that all operations on the connection would fail,
because the underlying COM+ transaction aborted. However, ODBC
operations continue, and succeed. After the error, the connection
apparently stops using the failed COM+ transaction and uses a
different transaction.

Is there some way I can force the ODBC connection to not resume
under a different transaction after the COM+ transaction fails?

Thanks,

Paul