Make sure that you do as little processing as possible within the actual transaction so that the transaction is short and sweet.
Other than that, there is absolutely no way a lock should be released before a transaction completes. >-----Original Message----- >REPOSTED FOR NON-MEMBER: Greg Livingston <[EMAIL PROTECTED]> > >I have a routine that runs in a transaction. Within the transaction I call a routine that >generates the next sequential number for the record key. The problem I'm having is >that one of my customer records has so many transaction to process that it holds the >lock on the key generation program and my other users then hang as they are waiting >for the record to unlock. Does anyone know a way of releasing the lock on a record >with in a transaction before the final commit? ********************************************************************** This email message and any files transmitted with it are confidential and intended solely for the use of addressed recipient(s). If you have received this communication in error, please reply to this e-mail to notify the sender of its incorrect delivery and then delete it and your reply. It is your responsibility to check this email and any attachments for viruses and defects before opening or sending them on. Spotless collects information about you to provide and market our services. For information about use, disclosure and access, see our privacy policy at http://www.spotless.com.au Please consider our environment before printing this email. ********************************************************************** ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
