Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Oracle Forms
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==History== {{unreferenced section|date=July 2011}} Oracle Forms is sold, and released separately from the [[Oracle Database]]. However, major releases of an Oracle database usually result in a new major [[software versioning|version]] of Oracle Forms to support new features in the database. === Interactive Application Facility (IAF) === Oracle Forms started as '''Interactive Application Facility (IAF)''', which had two main components: the [[compiler]] (Interactive Application Generator - IAG) and the [[runtime interpreter]] (Interactive Application Processor - IAP). Released with the first Oracle Database version 2 (there was no version 1), IAF provided a [[character (computing)|character]] mode [[user interface|interface]] to allow users to enter and query data from an Oracle database. It was renamed to '''Fast Forms''' with Oracle Database version 4 and added an additional tool to help [[source code generation|generate]] a [[default (computer science)|default]] form to edit with IAG, the form editor. It was renamed a third time to '''SQL*Forms''' version 2 along with the Oracle 5 database version. === Forms 2.x === Forms 2.0 included a forms design editor that included a [[screen generator|screen painter]]. This release was character-based (rather than GUI) so forms were developed and runtime typically in a terminal. The [[source file]] was an *.INP [[ASCII]] file and was edited using the screen painter, however the file was an ASCII file and editing this file directly in a text editor was a common practice due to the limitations of the form editor. This version of Forms did not include the [[PL/SQL]] language and instead it used its own custom language based on trigger steps. The language was more primitive than the PL/SQL language that was available in SQL*Plus. The limited language was augmented by [[user exit]]s that compiled language code linked to the [[binary file|binary]] of the Oracle-provided [[run-time system|run-time]]. Forms 2.3 was used as the basis for the Oracle Financials accounting package. As a result, 2.3 remained in use long after Forms 3 and 4 became available in order to support customer forms that were created to integrate with Oracle Financials. === Forms 3.x === Oracle Forms 3 was the first version to allow PL/SQL to be used within Forms triggers and procedures/SQL Functions could also be used as an undocumented feature. Forms 3 was a character mode application and was primarily used in terminals such as Digital VT220 and PCs running Microsoft DOS. It could run under [[X window system|X]] but did not support any X interface-specific features such as [[checkbox]]es, so it was basically a character mode application running in a GUI window. Although a mouse could be used to click on fields, there were no mouse specific triggers (such as when-mouse-double click) available in this release. The source file was an *.INP ASCII file. The runtime file was an *.FRM binary file. The IDE was greatly improved to allow editing of PL/SQL code, and this reduced the common practice of editing the INP source file directly. Forms 3 automatically generated Forms triggers and code to support some [[database constraint]]s such as primary keys and foreign keys. Constraints could be defined, but not [[wikt:enforce|enforce]]d in the Oracle 6 database at this time, so Oracle used Forms 3 to claim that it supported constraints in its technology stack. === Forms 4.0 === Oracle Forms version 4.0 was the first true GUI based version of the product that supported GUI elements such as checkboxes and radio groups in the Forms editor and at runtime. Although not publicly advertised, a character-based runtime was still available for certain customers on request. The arrival of [[Microsoft Windows 3]] and competitive products running under Windows forced Oracle to release this GUI version of Forms for commercial reasons. Forms 4.0 accompanied Oracle database version 6 with support for [[Microsoft Windows]] and X Windows. A new [[integrated development environment|IDE]] was introduced in this version. Each type of object had an editor window that was optimized for it, so the field editor looked quite different to the window editor. These would be abandoned in the next release and replaced with property sheets that were made popular with Visual Basic. The 4.0 source files were *.FMB for forms, *.PLL for libraries and *.OLB for object libraries the 4.0 runtime files were *.FMX for forms, *.PLX for libraries. *.OLB files were compiled into the FMX. The [[Oracle Financials]] software suite did not use this version of Forms and instead continued to use Forms 2.3. === Forms 4.5 === Oracle Forms version 4.5 was really a major release rather than a "[[point release]]" of 4.0 despite its ".5" version number. It was named 4.5 in order to meet contractual obligations to support Forms 4 for a period of time for certain clients so it could market 4.5 as being a patch to 4.0, even though a full install was required, rather than upgrading 4.0 to 4.5 with a patch. This version contained significant functional changes and a brand-new IDE, replacing the IDE that was introduced in 4.0. It added [[graphical user interface|GUI]]-based triggers, and provided a modern IDE with an object navigator, property sheets and [[code editor]]. This design had become popular at the time due to its use by Microsoft Visual Basic. The development environment has changed very little since this release, so a software developer that is experienced with Forms 4.5 can easily work on any version of Forms up to the latest version. === Forms 5.x === Oracle Forms version 5 accompanied Oracle database version 7. === Forms 6.x === Forms 6 was released with Oracle 8.0 database and was re-released as Forms 6i with Oracle 8i. This version was basically Forms 4.5 with some extra wizards and bug-fixes.<ref>{{Cite web |title=Oracle Forms Version History – A Timeline and Comprehensive Guide of How The Software Has Progressed |url=https://kumaran.com/blogs/oracle-forms-version-history-a-timeline-and-comprehensive-guide-of-how-the-software-has-progressed/ |website=Kumaran Systems|date=29 September 2023 }}</ref> It included the facility to run inside a web server. A Forms Server was supplied to solve the problem of adapting Oracle Forms to a [[three-tier]], [[web browser|browser]]-based delivery, without incurring major changes in its programmatic interface. The complex, highly interactive form interface was provided by a [[Java applet]] which communicated directly with the Forms server. However the [[World Wide Web|web]] version did not work very well over [[HTTP]]. A fix from Forms 9i was retrofitted to later versions of 6i to address this. The naming and numbering system applied to Oracle Forms underwent several changes due to marketing factors, without altering the essential nature of the product. The ability to code in Java, as well as PL/SQL, was added in this period. === Forms 9.x === The version number jumped straight from 6 to 9 in order to keep the number the same as the Oracle database version released at a similar time. Forms 9i included many bug fixes to 6i and was known as a good stable version. Support was removed for Windows client-server runtime, character-based interfaces and instead the three-tier, web browser-based user interface is the only deployment option. The ability to import java classes means that it can act as a [[web service]] client. Starting with this release the version number of Oracle Forms moving forward would keep in sync with the Oracle database version. As a result, version 8 as skipped, and the version number jumped to 9. After this release, there were very few product changes made besides keeping the version number in sync with the Oracle database. === Forms 10.x === Forms 10g is actually Forms version 9.0.4, so is merely a rebadged Forms 9i. === Forms 11.x === Forms 11 introduced advancements such as external events, JavaScript support in Release 1, and Access Manager, Real User Experience Interaction (RUEI), and performance monitoring in Release 2. These improvements expanded functionality and interaction capabilities, utilizing Oracle AQ to enable seamless interaction with [[Java Message Service|JMS]]. === Forms 12.x === Java Web Start allows users to run Oracle Forms applications without having a parent web browser. Although a browser may be used to initially obtain the application's Java Web Start launcher file (.Jalp), the browser is not responsible for hosting the application and can be closed after the application has been started. JWS supports Internet Explorer, Firefox ESR, Chrome, Edge. === Forms 14.x === Forms 14.1.2.0 was released on December 20, 2024.<ref name="Forms14">{{Cite web |last=Ferrante |first=Michael |date=December 20, 2024 |title=ANNOUNCEMENT: Oracle Forms and Reports 14.1.2 has been released. |url=https://forums.oracle.com/ords/apexds/post/announcement-oracle-forms-and-reports-14-1-2-has-been-relea-2394 |website=Oracle Forums}}</ref> There was no Forms 13, that version number was intentionally skipped due to 13 being considered an unlucky number in some cultures. New features include modernised widgets and support for accessing REST data sources.<ref name="RN14">{{Cite book |title=Oracle® Fusion Middleware: Release Notes for Oracle Forms 14.1.2.0.0 |chapter=What's New in this Release |url=https://docs.oracle.com/en/middleware/developer-tools/forms/14.1.2/releasenotes-fnr/whats-new-this-release.html |access-date=2025-01-04 |language=en-US}}</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)