Document-ID: 28932.1
Subject: UPGRADING TO FORMS 4.5
Author: RMONGE
Last Modified Date: 21 June 1995
INTRODUCTION
============
This document provides a step by step guide on how to convert forms
from older version of Forms, such as 2.3, 3.0, and 4.0, to Forms 4.5.
UPGRADING FROM SQL*FORMS 2.3/3.0
================================
Upgrading from older versions of Forms is a simple process; but it requires
that you follow a series of steps and that you have Forms tables installed
in the database in some cases.
If you are upgrading from an older forms versions such as 2.3 or 3.0, this is
what the upgrade process will do:
1. Take the .inp file and read it according to the format you specify and
convert it to an .fmb (binary) file.
2. Convert fields to text items.
3. Convert pages to canvas-views.
4. Convert LOVS (list of values) to Forms 4.5 LOVS and record groups
accordingly.
5. Change trigger names names if applicable.
(e.g. ON-VALIDATE-ITEM trigger changed to WHEN-VALIDATE-ITEM)
When converting the triggers, Forms 4.5 generator will not change the trigger
text, it will only change the trigger name.
To upgrade, you need to invoke the Oracle Forms Generator either by double-
clicking on the Forms Generator icon in windows, or, in UNIX, using the
F45genm (motif). You CAN set the following options:
FILE: Name of the Forms 2.3. application (.inp)
USERID: Name of the User
PASSWORD: Password of the User
DATABASE: Database connect string
MODULE TYPE: FORM (DEFAULT)
MODULE ACCESS: FILE (DEFAULT)
UPGRADE 3.0 FORM... [X] CHECKED
VERSION TO UPGRADE 23
Using the command line you can type the following:
f45gen module=filename userid=un/pw upgrade=yes version=23
To upgrade from Forms 3.0 the only value that would change is the VERSION
number; however, there is no need to specify the version number when
upgrading from Forms 3.0.
When upgrading from a character mode to GUI mode, you will notice that
all fields include a bevel to produce a three-dimensional look. The bevel
may take up to 1/2 characters per field on some operating systems; the
result is that the fields do not display their full value.
To fix this problem, you need to use the parameter WIDEN_FIELDS. This
parameter adds one extra character to the width of the text item or field to
allow more space for the bevel. However, you need to be aware of some possible
problems:
- If the text items are next to each other horizontally with no space in
between them, the items will overlap when the form is upgraded.
- If the text items are next to each other horizontally with only one space,
then the text items will have no space in between them.
If you want to use this option, you need to set it in the Oracle Forms
Generator as shown below:
WIDEN FIELD DISPLAY LENGTH BY ONE WHEN UPGRADING? [X] CHECKED.
Or, at the command line:
f45gen module=name userid=scott/tiger upgrade=yes widen_fields=yes
Note: This option is set to NO by default.
UPGRADING FROM FORMS 4.0 TO FORMS 4.5
=====================================
It is a good idea to have a backup of all .fmb files that you will be
upgrading to Forms 4.5. Once the (.fmb) files are saved as Forms 4.5 files,
they cannot be open in Forms 4.0.
The upgrade process from Forms 4.0 consists of two steps:
1. Open the form in the Forms 4.5 Designer.
2. Save it to the .fmb file again or to the database.
You can also create a Forms 4.5 executable out of a Form 4.0 .fmb file and
keep the source as a Forms 4.0 file. To do this, perform the following steps:
1. Open the Form 4.0 in the Forms 4.5 Designer.
2. Select ADMINISTRATION--->GENERATE to create a executable (.fmx) without
making any changes to the (.fmb) file.
At the command line, you can accomplish the same thing, using the following
syntax:
f45gen module=filename userid=scott/tiger
UPGRADING FORMS WITH REFERENCED OBJECTS
=======================================
To upgrade referenced forms, you must follow the next sequence of steps:
FORMS 3.0
=========
1. Make sure that the Forms 3.0 tables and Forms 4.5 tables exists in the
same database.
2. The source form must be saved into the Forms 3.0 tables.
3. Upgrade the form as normal and save it into the database.
Again, you need to bring up the Oracle Forms Generator either on Windows or
on Motif and set the following options:
FILE: Name of the forms application (.inp)
USERID: Name of the User
PASSWORD: Password of the User
DATABASE: Database connect string
MODULE TYPE: FORM (DEFAULT)
MODULE ACCESS: DATABASE
UPGRADE 3.0 FORM... [X] CHECKED
Forms 4.5 will check both FORMS 3.0 and Forms 4.5 tables in the database.
Hence, if there is a table or view missing, you will get ORA-942.
Note: See Bulletin# 106690.304 on how to install base tables for
Forms 3.0 and Bulletin# 108383.767 on how to install Forms 4.5 base tables.
FORMS 4.0
=========
Steps to upgrade forms referencing forms to Forms 4.5 :
1. In the Forms 4.0 Designer, open the source form from the database.
2. Save it to the file system (.fmb) file.
3. Open the form into the FORMS 4.5 Designer, and save it into the database.
4. Open the rest of the forms in the Forms 4.5 designer, and save them into
.fmb files or into the database.
QUESTIONS
=========
Q. After I convert a source form module to Forms 4.5, can I save it into the
filesystem?
Oracle Forms 4.5 allows the user to either reference objects in the database,
or in the file system. However, when you first upgrade your forms to 4.5,
all source forms used as reference are actually saved into the database, and
the forms modules that reference the source forms are looking for this
information into the database. To change the reference from database to
filesystem, follow the steps below:
1. In the Forms 4.5 Designer, open the source form from the database and
save it to the filesystem.
2. Open the form containing the referenced objects. Then, bring up the
property sheet of the reference object.
3. Double-click on a property called REFERENCE INFORMATION; this will bring a
dialog window with the referenced information.
4. Change the properties as needed:
e.g.
DATABASE FILESYSTEM
MODULE: SCOTT.EMP EMP
TYPE: FORM FORM
ACCESS: DATABASE FILESYSTEM
OBJECT NAME: EMP EMP
5. Click OK, and save the form module to the filesystem.
Q. Is there a way to change the reference from database to filesystem
globally?
A. This option is not yet available.
REFERENCES:
===========
Oracle Forms 4.5 Reference Manual Volume 2.