> I'm having the same problem you reported, but only when connecting to an
> Oracle 10.2 database. Our code works fine on earlier versions of Oracle as
> well as DB2 and SQL Server. Did you ever figure out what the problem was and
> how to resolve it?
Yes. The cause was unexpected. The short answer was that while
inside a transaction I was re-assigning a recordset object variable to
point to a newly instantiated recordset object without first closing
the recordset object that previously pointed to. ADO didn't like
this, so it purposely passed an invalid SQL statement to the server so
that the server would be forced a rollback of the entire transaction.
The statement: "SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER
TO UNPREPARED STATE;" is what ADO passed to the server to force an
exception.
Although I have only experienced this project with reassigning opened
recordset object references, I would expect and reassigning other
opened ADODB object would produce the same result.
--
Regards,
Richard Broersma Jr.
Visit the Los Angles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug
--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc
No comments:
Post a Comment