When generating Navigator Form, CG$STARTUP_MODE not generated

Question

Hi all,
We are using Desesigner 6.4.2 and Headstart, and I try to generate a Navigator Form. In this case, the generator does not generate the parameter CG$STARTUP_MODE.
Running the fmx, an error message pops up saying: FRM-47023: No such parameter named cg$startup_mode exists in form ...
This error is raised during the PRE-FORM trigger.
When using the the preference set QMS65_DEBUG_MODULE, this error does not occur. This convinces me that there is a bug in the delivered Headstart libraries.
Thanks in advance,
Joep Hendrix

Answer 1

All,
Tonight I added the following text to bug 2309202 in the bug database on this topic:
start *************************************************************************************
Suggested workaround for this bug does not work because of another bug: 2391990. When the cg$startup parameter is not generated, all user defined arguments at module will not be generated neither.
Since it is not possible to generate a parameter cg$startup_mode into a form by adding it to the template form in advance (OFG ignores template form parameters starting with CG$), the only workaround for the problem with cg$startup mode seems to be to make the headstart library code robust for the lack of this parameter, using built in qms$errors.add_suppress_message('FRM-47023').
However, the problem is caused by OFG (bug 2391990), not headstart.
end *************************************************************************************
Also I logged bug 2391990 on Oracle Form Generator, that is referred to. Bug text for this bug:
start *************************************************************************************
BUG 2391990 - OFG GENERATOR DOES NOT GENERATE PARAMETERS FOR ARGUMENTS IN READ ONLY FORMS
Since release 4.2 of Designer 6.5, form generator sometimes does not generate
parameters for user defined arguments. On top of that, parameter
cg$startup_mode is also not generated in this case.
This makes the suggested workaround for bug 2309202 useless.
How to reproduce
================
Use designer (I used some wizards) to
- create a table definitaion named TEST
- add columns (id number(10) not null, name (30))
- add a primary key on column id.
- create a module named TESTMOD (Oracle Forms)
- add a module component named TEST, insert=no, update=no, delete=no
- add a table usage on table TEST
- add bound items for columns id and name display length 10 resp. 30 and
properties insert=no, update=no for both columns
- add an argument p_test at module level, varchar2, length=50, default
value=test
- generate the module for the 1st time. Notice that parameters cg$startup_mode
and p_test are generated.
- now, change the display length of bound item id from 10 to 15
- generate the module again. Notice that parameters cg$startup_mode and p_test
are -NOT- generated!
- change the bound item length back from 15 to 10 for id
- Set the module component properties insert=yes, update=yes, delete=yes (do
not touch the insert/update property at bound item level)
- generate the module again. Notice that in this case the parameters
cg$startup_mode and p_test are NOT generated
- Set the bound item properties insert=yes, update=yes for id and name
- generate the module again. Now the parameters are correctly generated.
The behaviour seems intermittently, but is reproducible every time the
specification is exactly the same as before.
The above scenario was tested with AND without making use of the Headstart
template package set. This did not affect the outcome: in both cases the
errors did occur.
It is not possible anymore to rely on the correct generation of the argument
and named passed value mechanism of OFG.
end *************************************************************************************
Regards, Marc
P.S. Rob Kelder is an Oracle Employee.