Re: Best point to commit in a Master/Dtl Form

You did not indicate which tool was being used (forms 2,3,4,..) If you create a database constraint on the detailed table and select Use Constraints when building the Detailed block in forms 3.x you would get ON-VALIDATE-FIELD triggers which would do the duplicate test for you.

Option 1) will not let the user cancel and rollback their change when they navigate to the next block. I recommend option 2) with on-validate-field triggers to test for duplicates. This allows you to make the test when the user inserts or updates the field and before the use commits any data.

Malh1156 (malh1156_at_aol.com) wrote:
: Hi,
: I am trying to ascertain when should I commit a record in a
: Master/Detail
: Form.
: 1) I can commit the master block as I navigate to the detail block, and
: subsequently
: commit each detail row as I navigate to the next row.
: OR
: 2) wait till the operator is done and then commit all records then when
: he presses save button.
: which one is better?
: If I implement 1), it is easy to check for duplicate records entered in
: the detail block as user enters them.
: But giving an explicit SAVE button to could be tricky.
:
: If I implement 2) then I am not sure If I can detect for duplicate
: records entered into the detail block till the operator TRIES to commit..
 

: I think I am missing something.
: Thanks in advance,
: Rajiv

--
This posting represents the personal opinions of the author. It is not the
official opinion or policy of the author's employer. Warranty expired when you
opened this article and I will not be responsible for its contents or use.