Note:If you are upgrading from releases of Forms before Forms 6i to Oracle Forms 11g, you must first upgrade your applications to Forms 10g (10.1.2), and then upgrade them to Oracle Forms 11g.
Note:Before converting your forms or menus, it is recommended that you first make backup copies of all files. Once you upgrade a module, the module cannot be opened in an earlier version of Forms Developer.
To upgrade a version 4.x or 5.x Forms application to Forms 10g (10.1.2):
Start Forms 10g (10.1.2).
Choose File | Open to display the file.
Choose the module you want to upgrade.
Choose File | Save.
Choose Program | Compile | All to compile the upgraded module.
Note:All form modules and libraries must be upgraded and recompiled.
In order to streamline the tools available and simplify the development process for building Forms applications, the option of saving files to database has been removed. In Forms 6i, modules could be saved in the database. For all releases after 6i, module files that were saved in database must be saved to the file system.
Open the prior version of Forms.
Save the module files to the local file system.
Upgrade the files as described in Section 16.1, "Upgrading a Form".
If you have client-side program units written in PL/SQL V1 or V2, you must convert that code to the new level.
Stored program units can use all the PL/SQL features that are valid for use in client side PL/SQL. Certain PL/SQL features such as the supplied DBMS_LOB routines or DBMS packages that are specified as pragma interface (C, C++, etc) cannot be directly called from Client Side PL/SQL. Forms programs must call a stored procedure which in turn calls the routine in question in these restricted cases.
The default run-time behavior of forms created with Forms 5.0 through 6i differed from run-time behavior for Forms 4.5. The form-level Runtime Compatibility Mode property could be set to "4.5" to provide Forms release 4.5 behavior. (This happened by default in forms that were upgraded from Forms release 4.5.)
Starting with Forms Developer, 5.0 behavior is used in all cases, and the form-level property "Runtime Compatibility Mode" is ignored.
If you are upgrading a form that specifies 4.5 behavior to Oracle Forms, you must alter the logic, as necessary, to reflect the differences between 4.5 and 5.0 behavior. See the Forms 11g Release 2 online help for information about the Runtime Compatibility Mode property and the differences between 4.5 and 5.0 behavior.