|
Re: save button(updation) [message #512075 is a reply to message #512033] |
Thu, 16 June 2011 16:48 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
cookiemonster
Messages: 13937 Registered: September 2008 Location: Rainy Manchester
|
Senior Member |
|
|
You need to give an example. What gets updated?
Why do you have two blocks?
What is the relationship between the blocks?
How is the data from the two blocks used to do the update?
|
|
|
Re: save button(updation) [message #512097 is a reply to message #512075] |
Fri, 17 June 2011 00:04 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) |
![](http://www.orafaq.com/forum/images/custom_avatars/72104.gif) |
Littlefoot
Messages: 21818 Registered: June 2005 Location: Croatia, Europe
|
Senior Member Account Moderator |
|
|
This is how I see it: it seems that these blocks act as if they were "master-detail". As the "upper" block is a control block, it is not based on a table. In order to save control block's values into that table, you (Rajendaroracle) must have written an INSERT statement, somewhere (I presume in WHEN-BUTTON-PRESSED trigger on that "Save" button).
Now, as they are master and detail blocks, detail block contains the same items as the master block, but they are (probably) hidden. Never mind, they contain the same values as master block's ones. As the detail block is a database block, COMMIT_FORM saves detail's records into a table. It means that they are "duplicated" (sort of; I suppose that master block's records saved into a table miss some columns' values).
So, from my point of view, all you have to do is to remove INSERT statement that is responsible for inserting master block's values into the table.
On the other hand, if I was wrong, answer Cookiemonster's answers, one by one and we'll see what next.
|
|
|