This table describes how different combinations of the BATCH, UPGRADE, and UPGRADE_PLSQL parameters affect the conversion process:
BATCH |
UPGRADE_PLSQL |
UPGRADE |
Behavior |
---|---|---|---|
NO |
YES |
YES |
PL/SQL in form is converted in batch mode (even though BATCH=NO). |
YES |
YES |
YES |
PL/SQL in form is converted in batch mode. |
NO |
NO |
YES |
PL/SQL in form is not converted, but a List of suggested conversions is written to module.plg. The rest of the form is upgraded to the current release Oracle Forms. |
YES |
NO |
YES |
PL/SQL in form is not converted, but a List of suggested conversions is written to module.plg. The rest of the form is upgraded to the current release Oracle Forms. |
NO |
NO |
NO |
Used to compile a new FMX without modifying the FMB. If the form contains 1.3 PL/SQL, you may see compiler errors, or the behavior of the code may be different. |
YES |
NO |
NO |
Used to compile a new FMX without modifying the FMB. If the form contains 1.3 PL/SQL, you may see compiler errors, or the behavior of the code may be different. |
Important:
If you are upgrading from FMT to FMB and you do not specify the UPGRADE_PLSQL option, the PL/SQL in the form is not converted, but a List of suggested conversions is written to a log file. This log file is placed in the current working directory, which may be different from the directory in which the FMT file is located.