I am not sure it can be done easily. But if you change an item value by using LOV then detail block is populated by default - see "Coordination property" in the Forms on-line help and how it can be modified.
Maybe you can try
1. to remove
Add_Parameter(pl_id, 'ORACLE_SHUTDOWN', text_parameter,'Yes');
2. and also put messages for checking values of parameters
Add_Parameter(pl_id, 'p_stat_id', text_parameter, ''''||:parameter.p_stat_id||'''');
message(:parameter.p_stat_id);
pause...
There are both Oracle9i Forms Technical Information and Oracle Forms Release6i Technical Information
in http://otn.oracle.com/products/forms/content.html
there.
There can be a block with insert/update allowed = yes and all it's items are insert/update allowed = no.
You can perform validation also in Pre-Insert and Pre-Update triggers, I use this method.
Helena
Commit_Form built-in saves your changes to the database. Of course only in your second data block records can be inserted and updated (block and item properties Insert Allowed and Update Allowed).
I hope this will help you.
Helena
I advice you to use Oracle Forms6i/Reports6i. I work with it and I think that it can satisfy all your needs. It can run also on WEB ...
Here you can find more about it (also demo):
http://technet.oracle.com
I hope this will be a little help for you.
Helena
During creation of an unbound item in Designer you can specify Display Type property - Drilldown current record in your case. You can do it in Property Palette, too.
Hehenka
OPEN_FORM can be used to open a query-only form. If the form that issues the OPEN_FORM built-in is running in QUERY_ONLY mode, then the opened form will also run in QUERY_ONLY mode.
The difference between OPEN_FORM and CALL_FORM is that CALL_FORM runs an indicated form while keeping the parent...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.