Oracle Forms is awash and appear alone from the Oracle database. However, above releases of an Oracle database usually aftereffect in a fresh above adaptation of Oracle Forms to abutment fresh appearance in the database.
The aboriginal adaptation of Oracle Forms was called Alternate Application Adeptness (IAF). This had two capital components, the compiler (Interactive Application Generator - IAG) and the runtime analyst (Interactive Application Processor - IAP). This provided a appearance approach interface to acquiesce users to access and concern abstracts from an Oracle database.
IAF was appear with Oracle Database Adaptation 2, the aboriginal bartering adaptation of Oracle. It was renamed to FastForms with Oracle Database adaptation 4 and added an added apparatus to advice accomplish a absence anatomy to adapt with accepted apparatus (IAG).
Renamed to SQL*Forms adaptation 2 with the Oracle 5 database.
Oracle Forms 2.3 was appearance based, and did not use PL/SQL. The antecedent book was an *.INP ASCII file. It was accepted for developers to adapt the INP book anon although that was not accurate by Oracle. This adaptation acclimated its own archaic and acrimonious congenital language, aggrandized by user exits—compiled accent cipher affiliated to the bifold of the Oracle-provided run-time
Oracle Forms 3 was appearance based, and was the aboriginal absolute adaptation of Forms, application PL/SQL. All consecutive versions are a development of this version. It could run beneath X but did not abutment any X interface specific appearance such as checkboxes. The antecedent book was an *.INP ASCII file. The IDE was awfully bigger from 2.3 which badly decreased the charge to adapt the INP book directly, although this was still a accepted practice. Forms 3 automatically generated triggers and cipher to abutment some database constraints. Constraints could be defined, but not activated in the Oracle 6 database at this time, so Oracle acclimated Forms 3 to affirmation abutment for administration constraints.
There was a "GUI" adaptation of Forms 3 which could be run in environments such as X Window, but not Microsoft Windows. This had no fresh activate types, which fabricated it difficult to attach PL/SQL to GUI contest such as abrasion movements.
Oracle Forms adaptation 4.0 was the aboriginal "true" GUI based version. A appearance based runtime was still accessible for assertive barter on request. The accession of Microsoft Windows 3 affected Oracle to absolution this GUI adaptation of Forms for bartering reasons. Forms 4.0 accompanied Oracle adaptation 6 with abutment for Microsoft Windows and X Window. This adaptation was awfully buggy and alien an IDE that was abhorred with developers. This adaptation was not acclimated by the Oracle Financialscomputer application suite. The 4.0 antecedent files were called *.FMB and were binary.
Oracle Forms adaptation 4.5 was absolutely a above absolution rather than a "point release" of 4.0 admitting its ".5" adaptation number. It independent cogent anatomic changes and a cast fresh IDE, replacing the abhorred IDE alien in 4.0. It is believed to be called 4.5 in adjustment to accommodated acknowledged obligations to abutment Forms 4 for a aeon of time for assertive clients. It added GUI-based triggers, and provided a avant-garde IDE with an article navigator, acreage bedding and cipher editor.
Due to adverse operational paradigms, Oracle Forms adaptation 5, which accompanied Oracle adaptation 7, featured custom graphical modes acquainted abnormally for anniversary of the above systems. However, its centralized programmatic interface remained system-independent. It was bound abolished by Forms 6.
Forms 6 was appear with Oracle 8.0 database; it was rereleased as Forms 6i with Oracle 8i. This was basically Forms 4.5 with some added wizards and bug-fixes. But it additionally included the adeptness to run central a web server. A Forms Server was supplied which apparent the botheration of adapting Oracle Forms to a three-tier, browser-based delivery, after incurring above changes in its programmatic interface. The complex, awful alternate anatomy interface was provided by a Java applet which announced anon with the Forms server. However the web adaptation did not assignment actual able-bodied over HTTP. A fix from Forms 9i was retrofitted to after versions of 6i to abode this.
The allotment and calculation arrangement activated to Oracle Forms underwent several changes due to business factors, after altering the capital attributes of the product. The adeptness to cipher in Java, as able-bodied as PL/SQL, was added in this period.
Forms 7 to 8 did not exist. These numbers were jumped over in adjustment to acquiesce the Oracle Forms adaptation cardinal to bout the database adaptation in v9.
Forms 9i included abounding bug fixes to 6i and was a abiding version. But it did not accommodate either client–server or character-based interfaces, and three-tier, browser-based commitment is the alone deployment best from actuality on. The adeptness to acceptation java classes agency that it can act as a web account client.
Forms 10g is absolutely Forms adaptation 9.0.4, so is alone a rebadged forms 9i.
Forms 11 will accommodate some fresh features, relying on Oracle AQ to acquiesce it to collaborate with JMS.
