PB - INFORMIX: How to not commit after an update?

Hello, all We have a situation involving updates not being rolled back. Environment PowerBuilder: 5.01 Transaction Object set using SetTransObject(), autocommit is set to false Informix: 7.2.2.UC1A5 Isolation Level: Committed read, logging is turned on INET Win 95 and Win 3.1 We use the PFC extensively in our code. We have seven datawindows(DW) linked together in one window. The collinkuse is set to filter. So, when we trigger an update, all DWs in the chain get updated. After all DWs are successfully updated, a COMMIT is issued. Looking at the DB after this, all updates are in tables. If a DW update fails, the application stops issuing updates. The application issues a rollback. This rollback does not stop successful updates from committing. Tested with non-PFC code, also. As soon as the DW update() returns successfully, the update is committed to DB. Any future rollbacks have no effect. Any suggestions to keep commit from taking place after update would be greatly appreciated. If email, please send to dhanse8@sears.com TIA, Dave -- Dave Hansen, CPD KDH Software, Inc. Email: kdhinc@mcs.com Kathy Hansen Elmhurst, IL USA Voice: 708.993.0889 The child must know that he is a miracle; that since the beginning of the world there hasn't been, and until the end of the world there will not be, another child like him. - Pablo Casals -- Dave Hansen, CPD KDH Software, Inc. Email: kdhinc@mcs.com Kathy Hansen Elmhurst, IL USA Voice: 708.993.0889 The child must know that he is a miracle; that since the beginning of the world there hasn't been, and until the end of the world there will not be, another child like him. - Pablo Casals