Hi friends.
Tis is the root cause ande the possible solutions:
The root cause:
The ODBC driver does not support transactions on a connection that has open sets of results. The result set must be opened and closed within the scope of the transaction. The ODBC driver does not preserve cursors in the transaction boundaries. This means that open result sets, but must be closed before entering or exiting the scope of a transaction. This is a limitation in the design of the ODBC driver used.
Recommended Solutions:
1. Check if there is an ODBC driver that does not have this limitation, and use it if exists.
2. Use DAO instead of RDO.
3. Rewrite the code to avoid this limitation. That is, that the result sets open but closed before entering or exiting the scope of a transaction.
It is not a backend problem, it corresponds to an error in the way you are programming, taking into account the limitations of the ODBC driver used.
Iván.