Oracle Forms开发详解

需积分: 3 33 浏览量更新于2024-08-01 收藏 660KB PDF 举报

"Oracle Forms是Oracle公司开发的一种用于构建客户端服务器数据库应用程序的图形用户界面工具。这个技术允许开发者创建用于展示和操作数据的表单。主要由三个组件组成：Form Builder、Form Compiler和Form Runtime。 1. Form Builder： Form Builder是Oracle Forms的核心设计工具，用于构建数据输入屏幕的设计和布局。通过它，开发者可以方便地创建事件驱动的PL/SQL代码，这些代码用于数据验证和导航。它包含以下几个关键特性： - 对象导航器：提供了一个层次化的浏览和编辑界面，帮助开发者快速定位和操作应用中的对象。 - 属性调色板：用于设置和修改表单模块中所有对象的属性，使开发者能够精细控制表单的外观和行为。 - 布局编辑器：是一个图形化设计工具，用于创建和排列应用中的界面元素和图形对象，实现用户界面的定制。 - PL/SQL编辑器：集成了Oracle过程构建器的功能，用于编写和调试与表单相关的PL/SQL代码。 2. Form Compiler： Form Compiler的作用是将Form Builder中创建的源文件编译成二进制文件，这个二进制文件可以在运行时执行。编译过程将源代码转换为高效且可以直接由Form Runtime执行的形式。 3. Form Runtime： Form Runtime是实际运行编译后代码的环境。它负责执行由Form Compiler生成的代码，处理用户交互，执行数据操作，并呈现表单给最终用户。在运行时，用户可以通过界面进行数据查询、更新和验证等操作。 Oracle Forms支持丰富的功能，包括自定义控件、数据验证、触发器、菜单、提示和警告等，使得开发者可以构建出功能强大且用户体验良好的企业级数据库应用。通过这些组件的协同工作，Oracle Forms为开发者提供了高效且灵活的数据库应用开发平台。"

Shik Mahamood Ali

Example:

Assume that you want to create a Key–NXTBLK trigger at the form level that navigates

depending on what the current block is. The following trigger performs this function, using

:SYSTEM.CURSOR_BLOCK stored in a local variable.

DECLARE

curblk VARCHAR2(30);

BEGIN

curblk := :System.Cursor_Block;

IF curblk = ’ORDERS’ THEN

Go_Block(’ITEMS’);

ELSIF curblk = ’ITEMS’ THEN

Go_Block(’CUSTOMERS’);

ELSIF curblk = ’CUSTOMERS’ THEN

Go_Block(’ORDERS’);

END IF;

END;

4. SYSTEM.MASTER_BLOCK

This system variable works with its companion SYSTEM.COORDINATION_OPERATION to help

an On-Clear-Details trigger determine what type of coordination-causing operation fired the

trigger, and on which master block of a master/detail relation.

5. SYSTEM.TRIGGER_BLOCK

SYSTEM.TRIGGER_BLOCK represents the name of the block where the cursor was located

when the current trigger initially fired. The value is NULL if the current trigger is a Pre- or

Post-Form trigger. The value is always a character string.

Example:

Assume that you want to write a form–level procedure that navigates to the block where the

cursor was when the current trigger initially fired. The following statement performs this

function.

Go_Block(Name_In(’System.Trigger_Block’));

Block – Based Triggers [Block Processing Trigger]

When-Create-Record, When-Clear-Block, When-Database-Record, When-Remove-Record

MASTER-DETAIL RELATIONSHIP

A master-detail relationship is an association between two data blocks that reflects a primary-

foreign key relationship between the database tables on which the two data blocks are based.

The master data block is based on the table with the primary key, and the detail data block is

based on the table with the foreign key. A master-detail relationship equates to the one-to-

many relationship in the entity relationship diagram.

A Detail Block Can Be a Master

You can create block relationships in which the detail of one master-detail link is the master

for another link.

What Is a Relation?

Shik Mahamood Ali

Coordination

You can control how the detail records are displayed when a master block is queried by setting

the coordination property. For example, you can defer querying the line items for an order

until the operator navigates to the item block.

Default [Immediate]

The default setting. When a coordination-causing event occurs, the detail records are fetched

immediately. (Deferred False, Auto-Query False)

Deferred with Auto Query

Oracle Forms defers fetching the associated detail records until the operator navigates to the

detail data block.

Deferred Without Auto Query

When coordination-causing event occurs, Oracle Forms does not automatically fetch the detail

records. To fetch the detail records, the operator must navigate to the detail data block and

explicitly execute a query.

Prevent Masterless Operation

Ensures that the detail data block cannot be queried or used to insert records when a master

record is not currently displayed.

Join Condition

Use to:

• Create links between blocks using SQL

• Alter links between blocks using SQL Define using:

• Usual SQL equi-join condition syntax

• Block names instead of the base table names

• Item names that exist in the form module instead of base table column names

 Master-detail triggers

On-Check-Delete-Master, On-Populate-Details, On-Clear-Details

RECORD GROUP

This object represents an internal Form Builder data structure that has a column/row

framework similar to a database table.

Query record group

A query record group is a record group that has an associated SELECT statement. The

columns in a query record group derive their default names, data types, and lengths from the

database columns referenced in the SELECT statement. The records in a query record group

are the rows retrieved by the query associated with that record group. Query record groups

can be created and modified at design time or at runtime.

Non-query record group

A non-query record group is a group that does not have an associated query, but whose

structure and values can be modified programmatically at runtime. Non-query record groups

can be created and modified only at runtime.

Static record group

Shik Mahamood Ali

A static record group is not associated with a query; instead, you define its structure and row

values at design time, and they remain fixed at runtime. Static record groups can be created

and modified only at design time.

Record Group built-in subprograms

Creating and deleting groups:

A] CREATE_GROUP (recordgroup_name VARCHAR2, scope NUMBER, array_fetch_size

NUMBER)

Creates a non-query record group with the given name

B] CREATE_GROUP_FROM_QUERY (recordgroup_name VARCHAR2, query VARCHAR2,

scope NUMBER, array_fetch_size NUMBER);

Creates a record group with the given name. The record group has columns

representing each column you include in the select list of the query

C] DELETE_GROUP (recordgroup_name VARCHAR2);

Deletes a programmatically created record group.

Modifying a group's structure:

ADD_GROUP_COLUMN (recordgroup_name VARCHAR2, groupcolumn_name

VARCHAR2,column_type NUMBER, column_width NUMBER)

Adds a column of the specified type to the given record group.

ADD_GROUP_ROW (recordgroup_name VARCHAR2, row_number NUMBER);

Adds a row to the given record group.

DELETE_GROUP_ROW (recordgroup_id RecordGroup, row_number NUMBER)

Deletes the indicated row or all rows of the given record group. Form Builder

automatically decrements the row numbers of all rows that follow a deleted row. When

rows are deleted, the appropriate memory is freed and available to Form Builder.

Populating Groups:

POPULATE_GROUP (recordgroup_id RecordGroup);

Executes the query associated with the given record group and returns a number

indicating success or failure of the query. Upon a successful query, POPULATE_GROUP

returns a 0 (zero). An unsuccessful query generates an ORACLE error number that

corresponds to the particular SELECT statement failure. The rows that are retrieved as

a result of a successful query replace any rows that exist in the group.

POPULATE_GROUP_WITH_QUERY (recordgroup_id RecordGroup, query

VARCHAR2)

Populates a record group with the given query. The record group is cleared and rows

that are fetched replace any existing rows in the record group.

SET_GROUP_CHAR_CELL(groupcolumn_id GroupColumn,row_number

NUMBER,cell_value VARCHAR2)

Sets the value for the record group cell identified by the given row and column.

SET_GROUP_DATE_CELL (groupcolumn_id GroupColumn, row_number NUMBER,

cell_value DATE);

Sets the value for the record group cell identified by the given row and column.

剩余87页未读，继续阅读

qg2

粉丝: 0
资源: 13

Oracle Forms开发详解

oracle-instantclient-12.2.0.1.0-1.x86_64 rpm包

oracle-instantclient11.2.x86-64.rpm.zip

ORACLE-AWR报告详细分析.pdf

Actualtests-Oracle-1Z0-147-V10.27.05.zip_Oracle数据库_PDF_

ORACLE--ERP--基础设置要点介绍.pdf

信息安全_数据安全_us-18-Nafeez-Compression-Oracle-.pdf

Oracle Database 21c (oracle-database-ee-21c-1.0-1.ol7.part3)

oracleasm-2.6.18-308.el5-2.0.5-1.el5.i686.rpm

oracleasm-2.6.18-53.el5-2.0.4-1.el5.i686.rpm

kmod-oracleasm-2.0.6.rh1-2.el6.x86_64.rpm

最新资源