Re: Locking problem?

Hi
on the Block or form property there will be an item called commit style or so.. and its default value is Immediate.. so when any one tries to update the row it will get locked . for this reason .. if you want to unblock the entries coming like insert you need to make this property to "Deferred" which will not block the row until the commit is issued. HTH
pradhan

Robert Garcia wrote:

> I have a Developer 2000, Windows NT, Oracle Server version 7,
> application that I execute update procedures out of a Validation
> Trigger. The problem is that the update procedure hangs - instead of
> executing an On Error Trigger - when one of the records to be updated
> is being edited in another instance of my application. A further
> description is as follows:
> When running two instances of my application, the first instance was
> locked onto (editing) a record that I knew that the second instance was
> going to update. When following the breakpoints of the second instance,
> it got to the update procedure (called out of the validation trigger)
> and the screen froze. I have 'on error' triggers set on the item that
> triggered the update procedure, on the block of this item. The 'on
> error' trigger will display an alert which will require a response from
> the user. None of these alerts was executed.
>
> What is happening is that my update (implicit) query is hanging - On
> Error trigger is not executed - because the record I am trying to
> update is locked by another user. Only when the first instance of my
> application disconnects will the update query run to completion.
> My gut feeling is that Oracle never expected Update Queries to be
> executed out of validation triggers. Has anyone been able to do this?
Received on Wed Nov 24 1999 - 02:10:28 CET