Hi Jef
>We have a user who dials in over a modem. They lose the phone connection >in the midst of a database transaction - before the commit or rollback. >I do not understand why, but they find that some records are updated and >some are not. It is not what I would expect, but losing the "client" >like that in a client-server application is not good. The Transaction should rollback if the client drops out. I would Check that you have the transaction boundaries correct, the updated records may be outside of the transaction boundary and thus not effected by transaction rollback. (ie The Update is before the Transaction Start). Are the transaction control written into the client program or in a subroutine that is called by the David Jordan Managing Consultant [EMAIL PROTECTED] www.dacono.com.au ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
