Transaction Management on Server

We're having a problem with the Informix database when a client terminates the connection in the middle of a transaction. Here is the scenario: User updates a grid control with 50 new items Client starts transaction and begins to loop through the 50 updates After about 30 seconds of the wait cursor User think PC is hung User reboots client machine .....Transaction never ended processed 42 records No new client requests can be processed until DBA kills process We tampered with the Alt-Ctrl-Del message so the User couldn't warm boot the PC, but they just hit the power switch!! With Sybase we were able to write an OpenServer that handled this problem, by having it take an array of parameters and a stored procedure name. The OpenServer running on the server took the request began a transaction, looped through the array, ended the transation. Unless the server went down the transaction always was commited (or rolled back). Is there a way to do something like this for Informix? John --------------------------------------------------- "I still haven't found what I'm looking for." U2 sitting on the curb of the Information Highway....