How It Works
Oracle Forms accesses the Oracle database and generates a screen that presents the data. The source form (*.fmb) is compiled into an "executable" (*.fmx), that is run (interpreted) by the forms runtime module. The form is used to view and edit data in database-driven applications. Various GUI elements, such as buttons, menus, scrollbars, and graphics can be placed on the form.
The environment supplies built-in record creation, query, and update modes, each with its own default data manipulations. This minimizes the need to program common and tedious operations, such as creating dynamic SQL, sensing changed fields, and locking rows.
As is normal with event driven interfaces, the software implements event-handling functions called triggers which are automatically invoked at critical steps in the processing of records, the receipt of keyboard strokes, and the receipt of mouse movements. Different triggers may be called before, during, and after each critical step.
Each trigger function is initially a stub, containing a default action or nothing. Programming Oracle Forms therefore generally consists of modifying the contents of these triggers in order to alter the default behavior. Some triggers, if provided by the programmer, replace the default action while others augment it.
As a result of this strategy, it is possible to create a number of default form layouts which possess complete database functionality yet contain no programmer-written code at all.
Read more about this topic: Oracle Forms
Famous quotes containing the word works:
“The works of women are symbolical.
We sew, sew, prick our fingers, dull our sight,
Producing what? A pair of slippers, sir,
To put on when you’re weary or a stool
To stumble over and vex you ... “curse that stool!”
Or else at best, a cushion, where you lean
And sleep, and dream of something we are not,
But would be for your sake. Alas, alas!
This hurts most, this ... that, after all, we are paid
The worth of our work, perhaps.”
—Elizabeth Barrett Browning (1806–1861)