Oracle® Forms Migrating Forms Applications From Forms 6i
10g (10.1.2.0.2) for Windows and UNIX B15572-01 |
|
Previous |
Next |
In order to streamline the tools available and simplify the development process for building Forms applications for the Web, Built-ins, constants, packages, and some syntax that are not applicable to Web deployment have been removed.
This chapter contains the following:
Menus associated with full-screen display and character mode have been removed. Code that contains these Built-ins will not compile and should be recoded, although exceptions are mentioned in the following table. Built-ins that are equivalent to obsolete Built-ins are also noted in the table.
Table 4-1 Obsolete Menu Built-ins
Obsolete Menu Built-in | Migration Notes |
---|---|
No migration path or replacement functionality. |
|
No migration path or replacement functionality. See Chapter 12, "Menu Parameters". |
|
No migration path or replacement functionality. |
|
No migration path or replacement functionality. Code containing this Built-in will compile but will not provide functionality. |
|
Use SET_MENU_ITEM_PROPERTY(). |
|
Use SET_MENU_ITEM_PROPERTY(). |
|
No migration path or replacement functionality. |
|
No migration path or replacement functionality. |
|
Use GET_MENU_ITEM_PROPERTY(<name>, ENABLED). Item_Enabled will work in Oracle Forms, but will be removed in a future release. |
|
No migration path or replacement functionality. |
|
Use CLEAR_ITEM. |
|
Use FORM_FAILURE flag. |
|
No migration path or replacement functionality. |
|
Use MESSAGE. |
|
Use NEXT_ITEM. |
|
No migration path or replacement functionality. See Chapter 12, "Menu Parameters". |
|
Use PREVIOUS_ITEM. |
|
No migration path or replacement functionality. |
|
Use SHOW_KEYS. The upgrade process will make this change automatically. |
|
Use FORM_SUCCESS flag. |
|
No migration path or replacement functionality. |
|
Use LOGOUT and LOGON. |
|
No migration path or replacement functionality. |
|
Use HOST. |
|
Use HOST. |
|
No migration path or replacement functionality. |
|
No migration path or replacement functionality. |
|
No migration path or replacement functionality. See Chapter 12, "Menu Parameters". |
|
No migration path or replacement functionality. |
|
No migration path or replacement functionality. |
|
No migration path or replacement functionality. |
|
No migration path or replacement functionality. See Chapter 12, "Menu Parameters". |
|
No migration path or replacement functionality. |
The following Built-ins have been removed. Code that contains these Built-ins will not compile and should be recoded, although exceptions are mentioned in the following table. Built-ins that are equivalent to the obsolete Built-ins are also noted in the table.
Table 4-2 Other Obsolete Built-ins
The following Built-in packages have been removed. Code that contains these packages will not compile and should be recoded, although exceptions are mentioned in the following table. Packages that are equivalent to the obsolete packages are also noted in the table.
Table 4-3 Obsolete Built-in Packages
Obsolete Package | Migration Notes |
---|---|
No migration path or replacement functionality because there is a new debugger. DEBUG.ATTACH and DEBUG.SUSPEND are still supported. |
|
No migration path. Use Forms Trace and Oracle Trace, which are documented in the book Oracle Application Server Forms Services Deployment Guide (Part No. B14032-01). |
The following constants used in the GET_ITEM_PROPERTY and SET_ITEM_PROPERTY Built-ins have been removed. Code that contains these constants will not compile and should be recoded, although exceptions are mentioned in the following table.
Table 4-4 Obsolete Constants
Obsolete Constant | Migration Notes |
---|---|
DATE_FORMAT_COMPATIBILITY mode |
Used by GET_APPLICATION and SET_APPLICATION properties. This constant is ignored. |
No migration path or replacement functionality. |
|
No migration path or replacement functionality. |
|
No migration path or replacement functionality. |