I got two data block. The first block in the master header, where I asked the user to enter the customer information and once finished entered, they need to pressed Save button to save the record.
The second block is the detail block where user needs to call the data from other view and pull the data into the tabular form. In here, I have created a delete button to delete the records where choose by user in the check box. Here the problem is when user press the delete button, the records in the previous master block is getting commit as well beside commit for the second block.
This is my script in the delete button.
IF :ACT_QT_TXN2.CHECK_BOX297 = 1 THEN
IF (:System.Last_Record = 'TRUE') and :ACT_QT_TXN2.CHECK_BOX297 = 1 THEN
IF (:System.Last_Record = 'TRUE') THEN
However, when I keep on press on the check box to select the record for delete again, the master block is not getting committed again. It is only commit on my first button clock on the delete button. How could this happened ? where is the possible problem ?
> previous master block is getting commit as well beside commit for the second block.
That is how Forms works. You cannot commit a single block. COMMIT (or commit_form) commits all pending changes in the Forms, not just one block.
>the master block is not getting committed again.
The first commit has saved the changes. If there are no new changes in the master block, there will be nothing to commit.
Sorry for the wrong statement mention. In fact my master block is getting committed again by create another record in the table when I press the save button.
I think I have solved my problem by putting one trigger in the master block of on-update as null. This will not created another record in master block when I saved my detail block.