Commit button [message #242101] |
Thu, 31 May 2007 11:29 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
sjcp21
Messages: 16 Registered: February 2007
|
Junior Member |
|
|
I have a custom form and the base table has a few non base table items.
Would there a be a problem with commit form button? i.e if I don't insert the records explicitly; on pressing the save button in the oracle applications , nothing gets saved?
how can i resolve that? I do want to make the non base table fields a part of that base table block.
thanks so much
|
|
|
|
Re: Commit button [message #242130 is a reply to message #242101] |
Thu, 31 May 2007 14:04 ![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) |
![](/forum/images/custom_avatars/72104.gif) |
Littlefoot
Messages: 21823 Registered: June 2005 Location: Croatia, Europe
|
Senior Member Account Moderator |
|
|
sjcp21 | base table has a few non base table items
|
Could you explain what you meant by that?
Whatever it is, in my opinion, if you have a table and want to use a form to store data into it, why don't you use all those columns as form items and make your life simple? You can, of course, use all non-database items and write a trigger to store values into a table (and that's not difficult; see the example), but - why?INSERT INTO your_table (empno, ename, job)
VALUES
(:emp.empno, :emp.ename, :emp.job);
COMMIT;
|
|
|
Re: Commit button [message #242157 is a reply to message #242101] |
Thu, 31 May 2007 16:07 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) |
hemavb
Messages: 103 Registered: May 2007 Location: Dubai , UAE
|
Senior Member |
|
|
In Forms if you are having non-db items as a part of your db block, make the Database Property > Database Item property of the Item as NO.
These items will neither be inserted, updated or queried from the database.
|
|
|