Oracle Forms and Reports

Major Forms Builder Tools

• Oracle’s Developer uses three different components:
• An Integrated Design Environment (IDE) called Forms Builder develops
forms. This tool places the desired design components into a binary file
with a file extension of .fmb. The binary form file cannot be executed until
it is turned into machine code.
• A Forms Compiler that creates a compiled (machine language) file based
on the form binary file. This file has an extension of .fmx. It is more
common, however, to compile the file within the Forms Builder tool.
• A runtime engine called Forms Server executes the compiled .fmx files in a
Web environment. Forms Server is a middleware product that receives
requests from a Web browser and dishes up a Java applet based on the
form to the browser
Executing Forms in Web-based Environment
• Web applications rely on a Web browser and a Web server.
• The Web server controls coordination. When using a form on the Web, the executable
file is registered with the Web server.
• To execute the Web form, a user requests a URL in his Web browser. The URL points to
an application registered within Forms Server. A listner on the Web server catches this
URL request and passes it to Forms Server. The Forms Server locates and executes the
.fmx file. It changes the .fmx file into a Java applet and sends it to the Web browser.
• To execute a form in a Web browser, the client unit must have an applet called JInitiator.
When an Oracle form is executed through the Web , the Web server storing the form
sends the Jinitiator applet to the client’s Web browser (if it does not already exist on the
client). Jinitiator is a generic applet, which is downloaded once to the client. It is actually
a plug-in that ensures the Web browser can interact with Forms Server. It is also used to
paint the form within the browser, validate data, and communicate with Forms Server.
Forms Server reads and executes the .fmx file. Forms Server communicates with the
database and with the applet on the Web browser
Installation
• After installing forms and report
• > Set Forms_Path
•>
• Setting Search Paths for Run Time
• Forms uses some environment variables set on the middle-tier machine to
search at run time for files such as forms, menus, and libraries. This enables
you to build applications that are portable across platforms and directory
structures by avoiding hard-coded paths in file references.
• Forms searches the following paths in order until the required file is found:
• The current working directory
• Directories in FORMS90_PATH
• Directories in ORACLE_PATH
• Although you could set these variables at the machine level, such as in the
Windows Registry, it is preferable to set them in the Forms environment file.
Settings in this file override system settings for running a Forms application.
Form Components
• Forms are composed of a variety of objects, but each form must have the following three
components:
• Data Block: this is the form object that contains data elements. The data block is usually
closely related to a database table or view. The data block elements receive database
values for display, update, or deletion. Data blocks also receive information that has been
input for insertion into the database. Data blocks generate dynamic SQL statements
(INSERT, UPDATE, and DELETE) that interact with the database.
• Canvas: This is the form object that is shown to the user and is displayed in the Layout
Editor. All displayed form components must be placed on a canvas to be displayed.
Canvases also contain graphic symbols and a boilerplate.
• Window: This is the form object that displays the canvas.
• These three components can be created manually using the Object Navigator, but it is
much more common to use the Data Block and Layout Wizards, especially for newly
created forms.
Data Blocks
• When you build database applications with Forms Builder, many of the blocks
will be data blocks. A data block is associated with a specific database table
(or view), a stored procedure, a FROM clause query, or transactional triggers.
• If it is based on a table (or view), the data block can be based on only one
base table, even though the data block can be programmed to access data
from more than one table and data sources. By default, the association
between a data block and the database enables the user to automatically
access and manipulate data in the database. However, to access data from
other tables (nonbase tables), you need to write triggers
• A form module is made up of one or more blocks. A data block is based on a
database object, such as a table or a view. A data block can contain both data
items and control items. A frame can be created to arrange data block items.
Each item in a block must appear on a canvas, and each canvas must appear
in a window. A form module can have one or more canvases and windows.
• Using triggers, you can add functionality to your form. Triggers can be written
at different levels in a form module. User-named program units enable you to
write additional PL/SQL code through procedures, functions, and packages.
Getting Started in the Forms Builder Interface
• Starting Forms Builder
• To start Forms Builder, invoke it from the Windows Start menu: Programs >
Oracle Developer Suite – iDS10g > Forms Developer > Forms Builder.
• Logging on to the Oracle Database
• Locate and select the Forms Builder option on the Start menu.
• If the Welcome to the Forms Builder dialog box opens, click the
Cancel button.
• When you are in the main work area, log on to Oracle by selecting
File/Connect menu option.
• Enter your Oracle ID information into the Connect dialog box. This
generally consists of the Oracle ID, password, and connect string. If
you are using an Oracle database that is installed on your PC, the
default ID is scott/tiger and a connect string is needed.
• Object Navigator: Locates and navigates to any form component. Double-clicking any object in the
Object Navigator causes Forms Builder to display the selected object within the appropriate
Forms Builder tool. The Object Navigator can also be used to create, delete, copy, and rename
form components. (can be launched by clicking F3).
• Property Pallete: Used to define special characteristics of the form’s components. Each
component has a different set of properties. Examples of component properties include case
restriction, length of value, data type, or prompt value. Properties can be used to substantially
control a form’s behavior. Double-clicking an object in the Object Navigator generally opens the
Property Pallette tool. (can be launched by clicking F4).
• Layout Editor: It paints the form. This tool allows you to move and arrange form objects, set font
and fill colors, add components to the form, and add a boilerplate. Doule-clicking ang graphic
component in the Object Navigator causes the layout Editor to display a canvas that contains the
graphic objects. (can be launched by clicking F2).
• PL/SQL Editor: Used to write the PL/SQL scripts needed by a form. These PL/SQL scripts are
placed in triggers associated to a form object or into program units that are embedded in the
triggers. A trigger is a PL/SQL code block whose execution is based on a form event, such as
double-clicking a form object, navigating to another text item, or pressing an F key. Program units
are PL/SQL scripts that are named and stored within a form or in a database. (can be launched by
clicking F11).
Property pallet
Layout Editor