The order I use is to build the key by using a routine, then cut the KEY record lock loose, followed by a RECORDLOCK on the transaction to be written. We do a similar function, and have not seen signficant wait times. If you're already doing that, I'm not sure what could be occurring.
john On 5/9/07, Moderator <[EMAIL PROTECTED]> wrote:
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? ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
-- john ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
