Escolar Documentos
Profissional Documentos
Cultura Documentos
Home page
1. Introduction
Here is a collection of Oracle Forms 10g sample dialogs extracted from a complete Oracle Forms tutorial.
This tutorial has been written in French and it would be too time consuming to translate it all in English.
This is the reason why I have only extracted and translated these sample dialogs.
The purpose of this article is not to teach how to build a new form from scratch. It intends to show some of the main advanced
features of the product.
To clearly understand in details how these dialogs work, you will have to open them in the Forms Builder and examine them
thoroughly.
However, in this article, I am going to explain the best I can the most important mechanisms of each sample.
These sample have been tested with an Oracle Forms 10g release 10.1.2.0.2 on an Oracle Database 10g Express Edition
Release 10.2.0.1.0.
TUTO_FORMS.FMB
This dialog is the entry point of the samples. Click on a button to start the corresponding dialog.
2.2 Canvases
TEST_CANVAS.FMB
Stacked canvas
A stacked canvas is displayed atop—or stacked on—the content canvas assigned to the current window. Stacked canvases
obscure some part of the underlying content canvas, and often are shown and hidden programmatically. You can display
more than one stacked canvas in a window at the same time
A stacked canvas allows to scroll a big canvas in a delimited window.
In this sample, the stacked canvas (CV_EMP_1) is twice bigger than its viewport.
Viewport
Viewport X position 77
Viewport Y position 11
Viewport Width 212
Viewport Height 138
Physical
Viewport X position on canvas 0
Viewport Y position on canvas 0
Width 212
Height 324
The second Stacked canvas (CV_EMP_3) demonstrates how to integrate in a Tab canvas:
2.3 Blocks
TEST_BLOC_VUE.FMB
This sample show how you can base a block on a view that aggregate the columns of several tables (in this case, DEPT and
EMP) and when you can insert, update and delete from the target tables from this view.
The code that handles the target table is located in a program unit, called from the three block-level triggers:
§ ON-INSERT
§ ON-UPDATE
§ ON-LOCK
PROCEDURE ins_upd_emp_dept IS
LN$Dummy PLS_INTEGER := 0 ;
BEGIN
-- Table DEPT --
Begin
Select 1
Into LN$Dummy
From DUAL
Where exists( select deptno from dept where deptno = :EMP_DEPT.DEPTNO ) ;
-- Found -> update --
Message('Update DEPT table');
UPDATE DEPT
SET DNAME = :EMP_DEPT.DNAME
WHERE DEPTNO = :EMP_DEPT.DEPTNO ;
Exception
When no_data_found Then
-- Not found -> insert --
Message('Insert into DEPT table');
INSERT INTO DEPT ( DEPTNO, DNAME )
VALUES ( :EMP_DEPT.DEPTNO, :EMP_DEPT.DNAME ) ;
End ;
-- Table EMP --
Begin
Select 1
Into LN$Dummy
From DUAL
Where exists( select empno from emp where empno = :EMP_DEPT.EMPNO ) ;
-- Found -> update --
Message('Update EMP table');
UPDATE EMP
SET ENAME = :EMP_DEPT.ENAME
WHERE EMPNO = :EMP_DEPT.EMPNO ;
Exception
When no_data_found Then
-- Not found -> insert --
Message('Insert into EMP table');
INSERT INTO EMP ( EMPNO, ENAME )
VALUES ( :EMP_DEPT.EMPNO, :EMP_DEPT.ENAME ) ;
End ;
END;
TEST_BLOC_PROC.FMB
§ A REF CURSOR
§ A PL/SQL table
In addition to that, there are also two different locations where to implement this functionality:
In this sample, the top block uses a REF CURSOR with the ON-xxx triggers
The bottom block uses a collection with the standard transactionnal triggers.
The stored procedures are located in the PKG_EMP package shipped with the scripts.
The Query Data Source Type is set to Procedure and the Query Data Source Name indicates the name of the query
procedure.
The insert, update, delete and lock orders are managed in the corresponding On-xxx triggers:
DECLARE
LR$Emp emp_pkg.emp_rec;
BEGIN
LR$Emp.empno := :emp.empno;
LR$Emp.ename := :emp.ename;
LR$Emp.job := :emp.job;
LR$Emp.sal := :emp.sal;
LR$Emp.comm := :emp.comm;
emp_pkg.emp_insert( LR$Emp );
END;
------------
-- Insert --
------------
PROCEDURE emp_insert(r IN emp_rec) IS
BEGIN
INSERT INTO emp (empno, ename, job, sal, comm)
VALUES(r.empno, r.ename, r.job, r.sal, r.comm);
END emp_insert;
The collection of records is an IN OUT parameter, read from the database and returned to Forms.
The insert, update,delete and lock orders are also managed by stored procedures.
(see them in detail in the EMP_PKG package)
Have also a look at the Query Data Source Column property that manages the relation between the columns of the
collection and the items of the block.
TEST_COLLECTION.FMB
In this dialog, we can see how to handle a table that contains a nested table (collection).
There is no standard buit-in to base a block on a collection, but we will see how easy it is to work with this sort of object via the
ON-xxx triggers.
(
EMP VARCHAR2(10),
QTE NUMBER
)
In this sample, the first block (ARTICLES) displays the standard columns of the ARTICLE table and the second block (detail)
displays the columns of its nested table.
The detail block (CASES) is dynamically populated each time a master record change in a When-New-Record-Instance of the
master block:
Declare
LC$Req Varchar2(256) ;
Begin
If :ARTICLES.CODE Is not null Then
-- Dynamic query of secondary block --
LC$Req := '(SELECT cases.EMP, cases.QTE FROM TABLE ( SELECT cases FROM articles WHERE code = '''
|| :ARTICLES.CODE || ''') cases)' ;
Go_Block('CASES' );
Clear_Block ;
Set_Block_Property( 'CASES', QUERY_DATA_SOURCE_NAME, LC$Req ) ;
-- populate the block --
Execute_Query ;
Go_Block('ARTICLES') ;
Else
Go_Block('CASES' );
Clear_Block ;
Go_Block('ARTICLES') ;
End if ;
End ;
Because it is not possible to create a new article with a NULL collection, we have to handle the insertion into the ARTICLE
table in a ON-INSERT trigger:
--------------------------------------------------------------
-- we are doing an explicit insert because the new record --
-- cannot contain a NULL collection --
--------------------------------------------------------------
INSERT INTO ARTICLES
(
CODE,
LIBELLE,
PRIX,
QTETOT,
CASES
)
VALUES
(
:ARTICLES.CODE,
:ARTICLES.LIBELLE,
:ARTICLES.PRIX,
:ARTICLES.QTETOT,
TAB_TYP_CASE() -- insert an empty collection
)
;
Indeed, if we insert a NULL collection, it will be no longer possible to insert anything in the nested table.
Then after, it is easy to manage the detail records with the ON-xxx triggers of the CASES block:
ON-INSERT:
WHERE
code = :ARTICLES.CODE
)
Values
(
TYP_CASE( :CASES.EMP, :CASES.QTE )
);
ON-DELETE:
etc.
TEST_DATA_SOURCES.FMB
I this sample dialog, we can see how to base a block on several tables that share an identical structure.
(see the JANVIER, FEVRIER and MARS tables created by the install.sql script)
The list item is populated with the name of three tables that share the same structure:
Then, the source table of the block is changed dynamically in the When-List-Changed trigger:
TEST_OBJETS.FMB
Let’s see how to manage an object table that contains a collection of references.
This sample is based on the object table (ARTICLE_OBJ) that contains a collection of references:
The tip is the same that the one used to manage the relational table with nested table:
- A when-New-Record-Instance trigger on the master block to populate the detail block (the collection of references):
Declare
LC$Req Varchar2(256) ;
Begin
If :ARTICLES.CODE Is not null Then
-- Dynamic query of secondary block --
LC$Req := '(SELECT emp.ref_emp.emp EMP, emp.ref_emp.qte QTE
FROM TABLE( SELECT REMP FROM articles_obj WHERE CODE = ''' || :ARTICLES.CODE || ''') emp
WHERE emp.ref_emp.art = ''' || :ARTICLES.CODE || ''')' ;
Go_Block('CASES' );
Clear_Block ;
-- change the Query Data Source Name --
Set_Block_Property( 'CASES', QUERY_DATA_SOURCE_NAME, LC$Req ) ;
-- populate the block --
Execute_Query ;
Go_Block('ARTICLES') ;
Else
Go_Block('CASES' );
Clear_Block ;
Go_Block('ARTICLES') ;
End if ;
End ;
-------------------------------------------------------
-- We are doing an implicit insert because the new --
-- record cannot contain a NULL collection --
-------------------------------------------------------
INSERT INTO ARTICLES_OBJ
VALUES
(
TYP_ARTICLES
(
:ARTICLES.CODE,
:ARTICLES.LIBELLE,
:ARTICLES.PRIX,
:ARTICLES.QTETOT,
TAB_REF_TYP_EMP()
)
) ;
The collection of references is managed with the corresponding ON-xxx trigger of the detail block:
ON-INSERT:
Forms_Ddl( LC$Req ) ;
End ;
ON-DELETE:
2.4 Items
TEST_ITEMS.FMB
TEST_LISTES.FMB
Let’s study and handle the three sorts of list item and also the different ways to populate them.
In this sample, the three list items are synchronized. Change the value of the first list and it will adapt the content of the
second then the content of the third.
For each new list value, the corresponding value and label are displayed.
a) The first list item is populated with the RG_MOIS record group:
-- List 1 --
errcode := Populate_Group( 'RG_MOIS' );
CLEAR_LIST('BLOC2.LISTE1');
POPULATE_LIST('BLOC2.LISTE1', 'RG_MOIS' );
-- Select the first value --
:BLOC2.LISTE1 := Get_List_Element_Value('BLOC2.LISTE1', 1 ) ;
CLEAR_LIST('BLOC2.LISTE2');
POPULATE_LIST('BLOC2.LISTE2', 'RG_SEMAINES' );
PROCEDURE Init_Liste3 IS
LC$D Varchar2(12) ;
LC$Day Varchar2(20) ;
BEGIN
End loop ;
Exception
When Others then
Null ;
END;
ALBUM_PHOTO.FMB
This dialog is the main part of the ensemble that allows to search, attach and display images.
You can build a photo album based on a one image’s column table.
It shows two ways to search a filename on the local machine with and without Webutil.
By clicking on a picture, you can navigate on another canvas to display the detail of the picture:
CHARGE_PHOTO.FMB
The get_file_name sample dialog is only a “pure exercice of style” , because it is so easy to pick-up a file with the
File_Open_Dialog() Webutil function.
This sample is interesting to see how to use the HOST() and TEXT_IO() functions to get the list of the local machine drives
and their content.
CHARGE_PHOTO_WEBUTIL.FMB
TEST_GRAPH.FMB
TESTS_CALCUL.FMB
2.5 Alerts
TEST_ALERTES_MESSAGES.FMB
This dialog shows how to use the Alert boxes to build the messaging engine of your Forms application.
The message texts are read from the database then displayed via Alert boxes.
To reduce the number of messages needed in the application, some of them can take from 1 up to 3 parmeters (%1, %2 and
%3). A pipe (|) character allows to split the message on several lines.
This sample use the Affiche_Message() procedure of the TUTO_FORMS pl/sql library to display the messages.
These messages can be displayed through the 3 alert boxes available in every dialog of this demo.
TEST_CLASSES_PROP.FMB
Let’s see some ways to use the property classes and the visual attributes to colorize and highlight dynamically different
objects of the form (alert, item, current record, etc.).
Property classes and visual attributes are located in the OBJ_TUTO_FORMS.olb object library.
TEST_CYCLES.FMB
This dialog allows you to understand what trigger fire and in what order when you use the application.
Before each particular action, you can clear the list of triggers window.
This window show you what trigger is firing in what order and from what block and what item.
3. Installation steps
§ Edit the /tutoforms/config/tutforms10g.env file to indicate your own settings (in blue in this example)
FORMS_PATH=%ORACLE_HOME%\forms\tutoforms
ORACLE_PATH=%ORACLE_HOME%\forms\tutoforms
FORMS_TRACE_PATH=%ORACLE_HOME%\forms\tutoforms
CLASSPATH=D:\Dev10gR2\forms\java\frmwebutil.jar;%ORACLE_HOME%\jlib\debugger.jar;%ORACLE_HOME%
\forms\tutoforms\FormsGraph.jar;%ORACLE_HOME%\forms\tutoforms\myIcons.jar;
§ Edit the /tutoforms/config/ add_to_formsweb.cfg file to set your own database connect string (in blue in this
example)
...
lookAndFeel=Oracle
colorScheme=blaf
logo=no
#don't forget to put your own database connexion
userid=tutoforms10g/tutoforms10g@XE
§ Then, you can start the demo by indicating the new [tutoforms10g] formsweb.cfg section.
http://machine:8890/forms/frmservlet?config=tutoforms10g