It would be useful, except that the problem is the locker causing the problem 
probably hasn't updated the record yet, which most likely would release the 
lock (this being an SB+ application) and end the problem.  Retaining the lock 
after an update is something that would likely be coded in unibasic.

-----Original Message-----
[] On Behalf Of Steve Romanow
Sent: Thursday, September 08, 2011 11:28 AM
To: U2 Users List
Subject: Re: [U2] Lock Status

On Thu, Sep 8, 2011 at 11:26 AM, Dave Davis <> wrote:
> It's a shame there isn't a file trigger operation on locking reads, just 
> updates and deletes.  That way you could just add it to the file in question.

The update trigger might be useful.  Most ppl would lock the record
before updating it.
U2-Users mailing list
________________________________ Dave Davis Team Lead, R&amp;D P: 614-875-4910 
x108 F: 614-875-4088 E: 
 6110 Enterprise Parkway Grove City, OH 43123 
This message is intended exclusively for the individual or entity to which it 
is addressed. This communication may contain information that is proprietary, 
privileged or confidential
 or otherwise legally exempt from disclosure. If you are not the named 
addressee, you are not authorized to read, print, retain, copy or disseminate 
this message or any part of it. If you have received this message in error, 
please notify the sender immediately
 by e-mail and delete all copies of the message.
U2-Users mailing list

Reply via email to