Re: Forms4.5 question -- 2 users accessing the same row in table

In article <01bc3e0c$58d958e0$050264c8_at_Shawno.erudite.com>,   "Shawn Odekirk" <shawno_at_erudite.com> wrote:
>
> > In testing, we have found that if one user is updating the document, the
> > others who try to show it get a Forms4.5 "error" saying something like the
> > data cannot be obtained, keep trying? You can click yes or no and then it
> > appears to continue trying to query the data.
> >
> > How can we avoid that situation? Do we issue some type of lock? Also, has
>
> Take a look at the Locking Mode property of your block.
> The default Locking Mode is Immediate. The online help recommends leaving the
> Locking Mode set to Immediate for Oracle databases and only using Delayed
> Locking Mode with non-Oracle databases.
> I have never used Delayed Locking Mode, but it looks like it may do what you
> need.
>
> Shawn

I checked out Delayed Locking mode once, and you have to be careful if you use it. If another user has locked a record on a form using the default immediate locking mode, the record remains locked until the user commits or rolls back. If the user of the delayed locking form tries to commit an update to the same row, the form locks up until the other user commits or rolls back.

Apparently in delayed locking mode, the form does a select for update, but without the NOWAIT option. I sure wonder who came up with this great idea. It renders using deferred locking mode useless in my opinion.

Regards,
Steve Cosner

-------------------==== Posted via Deja News ====-----------------------
      http://www.dejanews.com/     Search, Read, Post to Usenet