Re: Forms4.5 row locking

From: Lee levy <levy.lee.ls_at_bhp.com.au>
Date: 1995/12/06
Message-ID: <4a53l3$q67_at_merlin.resmel.bhp.com.au>#1/1

In article <DJ6IH5.1E9_at_CSUFresno.EDU>, stevec_at_zimmer.CSUFresno.EDU (Steve Cosner) says:
>
>I have a form which has a base-table block, and in the block, there is
>a non-base-table item. In a post-query trigger, the non-base-table
>item value is set. This causes the form to mark the row as changed,
>and locks the row in the database.
>
>This process prevents any other users from using the same form with
>the same data.
>
>Am I missing something obvious? What is the "right way" to accomplish
>this? Until the user actually changes an item from the base-table,
>I don't want the row locked.
>
>(We can work around it by setting up another block with the
>non-base-table items, but this requires a bit of extra work to keep
>both blocks in sync by row.)
>
>Are there some item properties on the non-base-table item to set to
>keep the form from locking the row?
>
>Please, anybody with some hints on this, could you pass them along?
>
>TIA,
>Steve Cosner

Steve,
I think you probably have set the Lock Record property on the non-base table item to True.
Set this to False and you should be fine.

Lee

---

      /\/\      :  Lee Levy, ISSD Systems Development
     / / /\     :  BHP Information Technology (WOLLONGONG REGION)
    / / /  \    :  PO Box 261, Warrawong, NSW 2502, Australia
   / / / /\ \   :  ACN 006 476 213
   \ \/ / / /   :  Telephone:  +61 42 75-5485  (tie-line 8855-)
    \  / / /    :  Facsimile:  +61 42 75-5500
     \/\/\/     :  Internet :  levy.lee.ls_at_bhp.com.au
====================================================================

Opinions expressed are my own and not necessarily those of either my employer or their clients Received on Wed Dec 06 1995 - 00:00:00 CET