Form Compiler options specify Oracle Forms default behavior during a Form Compiler session. Some of these options apply to file generation during development, for running and testing forms; other options apply only when you are converting files from earlier versions to Version 6.0.
You can set Form Compiler options in two ways:
The following chart lists the Form Compiler options from the "Form Compiler Options" window and their corresponding keyword parameters. For information on a specific Form Compiler option, see the corresponding parameter in the alphabetical list that follows the chart.
In the alphabetical list of Form Compiler parameters, the following information is shown for each parameter:
If you enter these keyword parameters as command line options, you can enter more than one at a time, in any order:
frmcmp module=myform userid=scott/tiger batch=YES
Option Name |
Keyword Parameter |
---|---|
File |
Module |
Userid/Password |
Userid |
Module type is Form, Menu, or Library |
Module_Type |
Logon to the database |
Logon |
Write script file |
Script |
Upgrade 3.0 Form or 5.0 Menu to 4.5 Module |
Upgrade |
Upgrade SQL*Menu 5.0 table privileges |
Upgrade_Roles |
Version to upgrade |
Version |
CRT file to use when upgrading |
CRT_File |
Compile a runform/runmenu file when upgrading |
Build |
Add key-up and down triggers when upgrading |
Add_Triggers |
Show help information |
Help |
Options_Screen |
Options_Screen* |
Batch |
Batch* |
*Use from command line only; not available from the Form Compiler Options dialog.