Foreign Key Locking Record

Question

In Form6i
Master Table Party (Party.fmx)
PartyCode,
Partyname
Transaction Table ( trans.fmx)
TNo,
TDate,
PartyCode,
Amount
one user is editing record in party
can other user insert or edit record in transaction form ?

Answer 1

Not sure this is the issue you are experiencing but here is my guess:
In Forms default behvior is to build an update statment for all db columns in the datablock, regardless of whether user changed those columns or not. So in your sample if the user updates the Amount column you might expect the update to be along the lines of the following pseudo code:
update transaction_table
set Amount = bind variable for amount field
where rownum = bind variable for current record
However, what it actually does is:
update transaction_table
set TNo = bind variable for TNo field,
TDate = bind variable for TDate field,
PartyCode = bind variable for PartyCode field,
Amount = bind variable for amount field
where rownum = bind variable for current record
So even though these fields were NOT changed they are included in the Forms update statement and the fact that you are updating the foreign key, PartyCode, column causes the db to get a lock on the Master Party table to validate the foreign key relationship. The way around this behaviour is the "Update Changed Columns Only" property at the block level in your form; if you set this property to "Yes" then it should prevent the update statement from including columns that the user did not change in the form.
The gotcha here is db trigger processing and keeping form data in synch with anything a trigger changed, I have seen some strange issues with triggers when doing this so if there are triggers on your transaction_table make sure they still behave as expected.
Again, not sure if this is what you are experiencing; hope it helps.
Wendell