From: Brian Leach
> ...Windows service app) in Delphi... Mutex wrapper... thread safe.
> ... Socket API or SOAP API... 

smart aleck.

> Seriously, if you are going to use transactions I would guess 
> the only way to avoid maintaining the key for the duration of 
> the transaction (to go back to the original post) would be to 
> take it out of the transaction space 

I don't like it, but it's better than your previous idea.
This seems to be an emerging theme:

From: [EMAIL PROTECTED]
> Could you call NEXT.AVAIL.ID before TRANSACTION START, and 
> again after the transaction rollback, assuming you can detect 
> if the transaction was rolled  back? 
> If the transaction committed, then no further action would be 
>  required.
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to