Top Banner
Oracle Form Builder
36
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Oracle Form Builder

Oracle Form Builder

Page 2: Oracle Form Builder

Module TypesModule Types

.FMB

.FMX .FMT

Form Module

.MMB .MMX .MMT

MenuModule

.PLL .PLX .PLD

PL/SQLLibrary

.OLB .OLT

ObjectLibrary

Page 3: Oracle Form Builder

Component

Window objects

Document WindowsMDI (Multiple Document Interface)

Dialog WindowsModal, Modaless

Các property đáng chú ý

Horizontal toolbar CanvasPrimary Canvas

Page 4: Oracle Form Builder

Form

Các property đáng chú ýMENU

Page 5: Oracle Form Builder

BlockA form module is made up of one or more blocks. A data block is based on a databaseobject, such as a table or a view. A data block can contain both data items and controlitems. A frame can be created to arrange data block items. Each item in a block mustappear on a canvas, and each canvas must appear in a window. A form module canhave one or more canvases and windows.

Data blockFrom Clause Query ex: id >10

Relation Object

• New relation object created in Object Navigator under master data block node

• Default name assigned: MasterDataBlock_DetailDataBlock

• Triggers and program units generated automatically

New RelationOnce you create a master-detail form module, the Data Block Wizard automaticallycreates a form object that handles the relationship between two associated data blocks.This object is called a relation. The following tasks occur automatically:• The new relation object is created under the master data block node in the Object Navigator with default properties.• The relation is given the following default name:

Page 6: Oracle Form Builder

MasterDataBlock_DetailDataBlock, for example ORDER_ITEM• Triggers and program units are generated to maintain coordination between the two data blocks.

Control blockSet_block_property(block_name, property, value1. value2);

Các property đáng chú ýDATABASE

Database Data Block Query Allowed Query Data Source Type

o Proceduceo Tableo From Clause

Insert/Update/Delete Allowed

Page 7: Oracle Form Builder

Canvas

Các loại canvas

Content

Stacked

Vertical ToolbarHorizontal Toolbar

What Is a Toolbar Canvas?A toolbar canvas is a special type of canvas that you can create to hold buttons andother frequently used GUI elements.The Three Toolbar Types• Vertical toolbar: Use a vertical toolbar to position all your tool itemsdown the left or right hand side of your window.• Horizontal toolbar: Use a horizontal toolbar to position all your toolitems and controls across the top or bottom of your window.• MDI toolbar: Use an MDI toolbar to avoid creating more than onetoolbar for a Form Builder application that uses multiple windows.Uses and Benefits of Toolbars• Provide a standard look and feel across canvases displayed in the same

Page 8: Oracle Form Builder

window.• Decrease form module maintenance time.• Increase application usability.• Create applications similar to others used in the same environment.• Provide an alternative to menu or function-key driven applications.Note: The MDI toolbar is only available for Microsoft Windows.

Canvas Property FunctionCanvas Type Specifies the type of canvas; for a toolbar canvas,set to Horizontal Toolbar or VerticalToolbarWindow Specifies which window the toolbardisplays inWidth Determines the width of the toolbarHeight Determines the height of the toolbarWindow Property FunctionHorizontal Toolbar Canvas/Vertical Toolbar CanvasIdentifies the horizontal/vertical toolbar todisplay in this windowForm Module Property FunctionForm Horizontal Toolbar Canvas/Form Vertical Toolbar CanvasIdentifies the horizontal/vertical toolbar todisplay in the MDI window

TabTab Canvas Related PropertiesOnce you create a tab canvas and its tab pages, you must set the required properties forboth of these objects. Place items on a tab page by setting the required item properties.Tab Canvas Property FunctionViewport X Position Specifies the X coordinate of the tab canvas upper-left cornerViewport Y Position Specifies the Y coordinate of the tab canvas upper-left cornerViewport Width Specifies the width of the view for the tab canvasViewport Height Specifies the height of the view for the tab canvasCorner Style Specifies the shape of the labelled tabs on the tab canvas (Selectfrom Chamfered, Square, and Rounded)Tab Attachment Edge Specifies the location where tabs are attached to the tab canvasTab Page Property FunctionLabel Specifies the text label that appears on the tab page’s tab atrun timeItem Property FunctionCanvas Specifies the tab canvas on which the item will be displayedTab Page Specifies the tab page on which the item will be displayed

Page 9: Oracle Form Builder

ItemINPUT ITEM

Text Item

Properties:Database Item(Yes or No)Check BoxRadio ButtonPoplistT-listCombo BoxList of Value

NONINPUT ITEMTextImageSoundPush ButtonIcon

Page 10: Oracle Form Builder

ToolCó 4 công cụ chính trong Oracle FormBuilder là

Layout Editor F2Object Navigator F3Properties Pallete F4PL/SQL F11

Property PaletteUnion/Intersection ModeFreeze/UnfreezeeCopy/Paste Properties

Object NavigatorHot key

Nhân bản một đối tượng Ctrl+D

Layout Editor

Run time

Các chế độ thực hiệnNORMAL

What You Can Do in Normal Mode• Retrieve all records.• Insert new records.• Update records.• Delete records.• Commit (Save) records.• Rollback (Clear) records.• Navigate outside of the current data block.• Exit the run-time session.What You Cannot Do in Normal Mode• Retrieve a restricted set of records.• Invoke the Query/Where dialog box.

ENTER QUERY

What You Can Do in Enter Query Mode• Retrieve all records.• Retrieve records by using selection criteria.

Page 11: Oracle Form Builder

• Retrieve records by using the Query/Where dialog box.• Obtain the number of records that will be retrieved before fetching themfrom the database by using Query—>Count Hits.What You Cannot Do in Enter Query Mode• Navigate out of the current block.• Exit from the run-time session.• Use certain functions, such as Next Record.• Insert new records.• Update existing records.• Delete records.

How to Use the Query/Where Dialog Box1 Do one of the following:- Select Query—>Enter.- Click Enter Query.- Press the appropriate function key.2 Enter a colon (:) followed by a unique character variable name in one ormore items.3 Do one of the following:- Select Query—>Execute.- Click Execute Query.- Press the appropriate function key.Note: Alternatively, you can select Query—>Count Hits if you simply want toknow how many records will match your criteria.The Query/Where dialog box is displayed.

Page 12: Oracle Form Builder

4 Enter the search criteria by using variables, SQL, and logical operators.5 Click OK.

QUERY

Các xác định form đang ở chế độ nào: SYSTEM.MODE = ‘ENTER-QUERY’ …

Debug

Page 13: Oracle Form Builder

Trigger, PL/SQL

TriggerTrigger ScopeThe scope of a trigger is determined by its position in the form object hierarchy, that is,the type of object under which you create the trigger.There are three possible levels:

Some triggers cannot be defined below a certain level. For example,Post-Query triggers cannot be defined at item level, because they fire due to a globalor restricted query on a block.

Trigger TypeThe trigger type determines which type of event fires it. There are more than 100 builtintriggers, each identified by a specific name.The name of a trigger identifies its type. All built-in trigger types are associated withan event, and their names always contain a hyphen (-). For example:• When-Validate-Item fires when Form Builder validates an item.• Pre-Query fires before Form Builder issues a query for a block.The first part of a trigger name (before the first hyphen) follows a standardconvention; this helps you to understand the general nature of the trigger type, andplan the types to use.

Trigger CodeThe code of the trigger defines the actions for the trigger to perform when it fires.Write this code as an anonymous PL/SQL block by using the PL/SQL Editor.Note: You only need to enter the BEGIN. . . END structure in your trigger text if you

Page 14: Oracle Form Builder

start your block with a DECLARE statement or if you need to code subblocks forother reasons.Statements that you write in a trigger can be constructed as follows:• Standard PL/SQL constructs (assignments, control statements, and so on).• SQL statements that are legal in a PL/SQL block; these are passed to the server for execution.• Calls to user-named subprograms (procedures and functions) in the form, a library, or the database.• Calls to built-in subprograms and package subprograms; these are procedures and functions that are part of Oracle Developer.Although you can include SQL statements in a trigger, keep in mind the followingrules about their use:• INSERT, UPDATE, and DELETE statements must be placed only intransactional triggers. These triggers fire during the commit process.• Transaction control statements (COMMIT, ROLLBACK, SAVEPOINT)cannot be included directly as SQL trigger statements. These actions arecarried out by Form Builder as a result of either commands or built-inprocedures that you issue.

Some trigger

Enter Query ModeUnrestricted and Retricted queries

Execute QueryCheck whether query is allowed on data blockPrompt to commit unsaved changes

Fire PRE-QUERY triggerBuild select statement

Fire PRE-SELECT triggerExecute select statement

Fire ON-SELECT triggerFire POST-SELECT triggerFire WHEN-CLEAR-BLOCK trigger

Fetch RecordCheck buffer already

Fire ON-FETCH triggerPOST-CHANGE Mark record and item as validPOST-QUERY Loop to fetch next record

When-New-” object “-Instance Triggers• When-New-Form-Instance: Khi startup form, Oracle Form tìm đến Item đầu tiên

trong block đầu tiên. Trigger này được gọi đầu tiên trong tất cả các trigger khi một form được bật lên. Trigger này không chạy khi bạn gọi trở lại form đã được

Page 15: Oracle Form Builder

gọi trước đó rồi. Trong ứng dụng có nhiều form thì việc chuyển focus qua lại giữa các form cũng không làm kích hoạt trigger này.

• When-New-Block-Instance: Trigger này được định nghĩa trên form hoặc block. Nó được gọi khi bạn chuyển từ item hiện tại tới một item của block khác.

• When-New-Record-Instance: Trigger này được định nghĩa trên form hoặc block. Nó được gọi khi bạn chuyển từ item của record này sang item của record khác.

• When-New-Item-Instance: Trigger này được định nghĩa trên form hoặc block hoặc item. Nó được gọi khi bạn chuyển focus tới một item.

The Pre- and Post- Triggers• Pre-Form: Pre-Form trigger được định nghĩa trên form, Pre-Form được gọi trong

quá trình startup form. • Post-Form: Pre-Form trigger được định nghĩa trên form, nó được gọi khi form đã

được bật lên và tiến tới thực thi việc thoát form. Nó thường được gọi để làm sạch form (clean up form) trước khi thoát.

• Pre-Block: được định nghĩa trên form hoặc block, được gọi trong quá trình mở form lên, hoặc trong quá trình chuyển từ block này sang block khác. Nó được dùng để:

Cho phép hay không cho phép access vào block ; set variable values;

• Post-Block: được định nghĩa trên form hoặc block, được gọi trong quá trình thoát khỏi block. Use a Post-Block trigger to validate the block's current record; that is, the record that had input focus when the Leave the Block event occurred. You might also use this trigger to test a condition and prevent the user from leaving a block based on that condition.

• Pre-Record: được định nghĩa trên form hoặc block, được gọi trong quá trình vào một record, hoặc khi chuyển tới một record khác. Use a Pre-Record trigger to keep a running total.

• Post-Record: được định nghĩa trên form hoặc block, được gọi trong quá trình thoát khỏi record. Nó cũng được gọi khi ứng dụng chuyển focus nhập từ một record sang một record khác. Việc thoát khỏi record có thể xảy ra như là kết quả của một trong các toán tử sau: INSERT_RECORD, DELETE_RECORD, NEXT_RECORD, NEXT_BLOCK, CREATE_RECORD, PREVIOUS_BLOCK...

Use a Post-Record trigger when you want to perform an action whenever the operator or the application moves the input focus from one record to another. For example, if

Page 16: Oracle Form Builder

you want to set a visual attribute for an item as the operator scrolls down through a set of records, you can do so from within this trigger.

• Pre-Item: Không tìm thấy• Post-Item: Không tìm thấy

Form trigger• PRE—FORM: đã có ở trên rồi.• WHEN-TIMER-EXPRIED: Fires when a timer expires. Timers are created

programmatically by calling the CREATE_TIMER built-in procedure.

• WHEN-NEW-FORM-INSTANCE: đã có ở trên rồi.• WHEN-NEW-BLOCK-INSTANCE: đã có ở trên rồi.• ON-POPULATE-DETAILS: được định nghĩa trên form hoặc block, Oracle

Forms creates this trigger automatically when you define a master-detail relation. It fires when Oracle Forms would normally need to populate the detail block in a master-detail relation.

• ON-MESSAGE: Fires whenever Oracle Forms would normally cause a message to display. Use an On-Message trigger for the following purposes:

· to trap and respond to an informative message

· to replace a standard informative message with a custom message

· to exclude an inappropriate message

• ON-ERROR: An On-Error trigger fires whenever Oracle Forms would normally cause an error message to display. Use an On-Error trigger for the following purposes:

· to trap and recover from an error

· to replace a standard error message with a custom message

• ON-CLEAR-DETAIL: được định nghĩa trên form hoặc block, Fires when a coordination-causing event occurs in a block that is a master block in a master-detail relation. A coordination-causing event is any event that makes a different record the current record in the master block. Oracle Forms creates the On-Clear-Details trigger automatically when you define a master-detail block relation.

Page 17: Oracle Form Builder

Block trigger• PRE-QUERY: được định nghĩa trên form hoặc block, Fires during Execute Query

or Count Query processing, just before Oracle Forms constructs and issues the SELECT statement to identify rows that match the query criteria.

• POST-QUERY: được định nghĩa trên form hoặc block, When a query is open in the block, the Post-Query trigger fires each time Oracle Forms fetches a record into a block. The trigger fires once for each record placed on the block's list of records.

• ON-POPULATE-DETAILS: đã có ở trên rồi.• ON-CHECK-DELETE-MASTER: được định nghĩa trên form hoặc block, Oracle

Forms creates this trigger automatically when you define a master-detail relation and set the Master Deletes property to Non-Isolated. It fires when there is an attempt to delete a record in the master block of a master-detail relation.

• WHEN-NEW-BLOCK-INSTANCE: đã có ở trên rồi.• WHEN-NEW-RECORD-INSTANCE: đã có ở trên rồi.• WHEN-CLEAR-BLOCK: được định nghĩa trên form hoặc block, Fires just before

Oracle Forms clears the data from the current block. Note that the When-Clear-Block trigger does not fire when Oracle Forms clears the current block during the CLEAR_FORM event.

. Use a When-Clear-Block trigger to perform an action every time Oracle Forms flushes the current block. For example, you might want to perform an automatic commit whenever this condition occurs.

· In a When-Clear-Block trigger, the value of SYSTEM.RECORD_STATUS is unreliable because there is no current record. An alternative is to use GET_RECORD_PROPERTY to obtain the record status. Because GET_RECORD_PROPERTY requires you to reference a specific record, its value is always accurate.

• WHEN-BUTTON-PRESS: được định nghĩa trên form hoặc block hoặc item, Fires when an operator selects a button, either by way of a key, or by clicking with a mouse.

• WHEN-MOUSE-LEAVE: được định nghĩa trên form hoặc block hoặc item, Fires after the mouse leaves an item or canvas-view if one of the following events occurs:

· if attached to the form, when the mouse leaves any canvas-view or item in the form

· if attached to a block, when the mouse leaves any item in the block· if attached to an item, when the mouse leaves the item

Page 18: Oracle Form Builder

• WHEN-MOUSE-ENTER: được định nghĩa trên form hoặc block hoặc item, Fires when the mouse enters an item or canvas-view if one of the following events occurs:· If attached to the form, when the mouse enters any canvas-view or item in

the form. if attached to a block, when the mouse enters any item in the block· if attached to an item, when the mouse enters the item

• KEY-DOWN

Item triggerText itemWHEN-VALIDATE-ITEM: được định nghĩa trên form hoặc block hoặc item, Fires during the Validate the Item process. Specifically, it fires as the last part of item validation for items with the New or Changed validation status.

Exception

Variable• PL/SQL variables must be declared in a trigger or defined in a package

• Form Builder variables– Are not formally declared in PL/SQL– Need a colon prefix in reference

• Items For presentation and user interaction:block_name.item_name

• Global variables Session-wide character variable:GLOBAL.variable_name

• System variables Form status and control:SYSTEM.variable_name

• Parameters Passing values in and out of module:PARAMETER.name

Form Builder VariablesThe following variables are available for the storage and manipulation of values:Initializing Global Variables with Default ValueYou can use the DEFAULT_VALUE built-in to assign a value to a global variable.Form Builder creates the global variable if it does not exist. If the value of theindicated variable is not null, DEFAULT_VALUE does nothing. The followingexample creates a global variable named country and initializes it with the valueTURKEY:Default_Value(’TURKEY’,’GLOBAL.country’);

Page 19: Oracle Form Builder

System variable:SYSTEM.variable_name (System)

i. :SYSTEM.MODE1. NORMAL2. ENTER-QUERY3. QUERY

ii. SYSTEM.LAST_QUERY1. Contains bind variables (ORD_ID = :1) before

SELECT_RECORDS2. Contains actual values (ORD_ID = 102) before

SELECT_RECORDSStatus

iii. SYSTEM.RECORD_STATUS (What is commit status?)1. NEW2. INSERT (also caused by control items)3. QUERY4. CHANGED

iv. SYSTEM.BLOCK_STATUS1. NEW (may contain records with status INSERT)2. INSERT (also possible for control block)3. CHANGED (block will be committed

v. SYSTEM.FORM_STATUS1. NEW2. QUERY3. CHANGED

Focus(Input Focus)

vi. SYSTEM.CURSOR_BLOCKvii. SYSTEM.CURSOR_RECORD

viii. SYSTEM.CURSOR_ITEMix. SYSTEM.CURSOR_VALUE

(Trigger Focus)x. SYSTEM.TRIGGER_BLOCK

xi. SYSTEM.TRIGGER_RECORDxii. SYSTEM.TRIGGER_ITEM

Page 20: Oracle Form Builder

Form Buider Built-in Sub-ProgramsThe Form Builder built-in subprograms belong to one of the following:• Standard Extensions packages: These built-ins are integrated into theStandard PL/SQL command set in Form Builder. You can call themdirectly, without any package prefix. You can use more than one hundredstandard built-ins.• Other Form Builder packages: Subprograms in other built-in packagesprovide functionality related to a particular supported feature. Theserequire the package name as a prefix when called.

Limits of Use• Unrestricted built-ins are allowed in any trigger or subprogram.

• Restricted built-ins are allowed only in certain triggers and subprograms called from suchtriggers

Example 1EDIT_TEXTITEM : Invokes the Form Runtime item editor for the current text itemENTER_QUERY: Clears the current block, and creates a sample record (Operators can then specify query conditions before executing the query with a menu or button command. If there are

Page 21: Oracle Form Builder

changes to commit, the Form Builder prompts the operator to commit them before continuing ENTER_QUERY processing.)EXECUTE_QUERY: Clears the current block, opens a query, and fetches a number of selected records (If there are changes to commit, Form Builder prompts the operator to commit them before continuing EXECUTE_QUERY processing.)EXIT_FORM Exits current form (or cancels query, if in ENTER-QUERY mode)

GO_FORMGO_BLOCK Navigates to the specified blockGO_ITEM Navigates to the specified itemGO_RECORD

GET_ITEM_PROPERTY : Returns specified property values for the specified itemSET_ITEM_PROPERTY : Changes setting of specified property for an item

• GET_APPLICATION_PROPERTY• SET_APPLICATION_PROPERTY•• GET_FORM_PROPERTY• SET_FORM_PROPERTY•• GET_RELATION_PROPERTY• SET_RELATION_PROPERTY•• SET_LOV_PROPERTY• GET_LOV_PROPERTY•• GET_TAB_PAGE_PROPERTY• SET_TAB_PAGE_PROPERTY•• GET_RECORD_PROPERTY• SET_RECORD_PROPERTY•• GET_WINDOW_PROPERTY• SET_WINDOW_PROPERTY•• GET_CANVAS_PROPERTY• SET_CANVAS_PROPERTY•• GET_VIEW_PROPERTY• SET_VIEW_PROPERTY•• GET_RADIO_BUTTON_PROPERTY• SET_RADIO_BUTTON_PROPERTY•• GET_MENU_ITEM_PROPERTY• SET_MENU_ITEM_PROPERTY

Page 22: Oracle Form Builder

•• SET_BLOCK_PROPERTY

• Get and Set:• DEFAULT_WHERE• ORDER_BY• QUERY_ALLOWED• QUERY_HITS

• Get only:• QUERY_OPTIONS• RECORDS_TO_FETCH

• GET_ITEM_INSTANCE_PROPERTY• SET_ITEM_INSTANCE_PROPERTY• GET_ITEM_PROPERTY• SET_ITEM_PROPERTY

• Get and Set:• CASE_INSENSITIVE_QUERY• QUERYABLE• QUERY_ONLY

• Get only:• QUERY_LENGTH

MESSAGE : Displays specified text on the message lineSHOW_ALERT Displays the given alert, and returns a numeric value when the operator selects one of three alert buttonsSHOW_EDITOR Displays the specified editor at the given coordinates and passes a string to the editor, or retrieves an existing string from the editorSHOW_LOV Invokes a specified LOV and returns a Boolean value, indicating whether user selected a value from the listSHOW_VIEW : Displays the indicated canvas at the coordinates specified by the X Position and Y Position of the canvas property settings (If the view is already displayed, SHOW_VIEW raises it in front of any other views in the same window.)

HIDE_VIEW

Object IDsFinding object idReferencing object by idReferencing object by name

Find_Build_InFIND_FORMFIND_BLOCKFIND_ITEMFIND_RELATIONFIND_LOV

Page 23: Oracle Form Builder

FIND_WINDOWFIND_VIEWFIND_CANVASFIND_ALERTFIND_EDITOR

DML Build-inCreate_RecordInsert_Reocord

Page 24: Oracle Form Builder

Validation

Validation ProcessForm Builder performs a validation process at several levels to ensure that records andindividual values follow appropriate rules. If validation fails, then control is passed back to the appropriate level, so that the operator can make corrections. Validation occurs at:• Item level: Form Builder records a status for each item to determine whether it is currently valid. If an item has been changed and is not yet marked as valid, then Form Builder first performs standard validation checks to ensure that the value conforms to the item’s properties. These checks are carried out before firing any When-Validate-Item triggers that you have defined. Standard checks include the following:

- Format mask- Required (if so, then is the item null?)- Data type- Range (Lowest-Highest Allowed Value)- Validate from List (see later in this lesson)

• Record level: After leaving a record, Form Builder checks to see whether the record is valid. If not, then the status of each item in the record is checked, and a When-Validate-Record trigger is then fired, if present. When the record passes these checks, it is set to valid.• Block and form level: At block or form level, all records below that level are validated. For example, if you commit (save) changes in the form, then all records in the form are validated, unless you have suppressed this action.

Page 25: Oracle Form Builder

Using Object Properties to Control ValidationYou can control when and how validation occurs in a form, even without triggers. Dothis by setting properties for the form and for individual items within it.The Validation UnitThe validation unit defines the maximum amount of data an operator can enter in theform before Form Builder initiates validation. Validation unit is a property of the formmodule, and it can be set in the Property Palette to any of the following:• Default• Item• Record• Block• FormThe default setting is item level. The default setting is usually chosen.In practice, an item-level validation unit means that Form Builder validates changeswhen an operator navigates out of a changed item. This way, standard validationchecks and firing the When-Validate-Item trigger of that item can be doneimmediately. As a result, operators are aware of validation failure as soon as theyattempt to leave the item.At higher validation units (record, block, or form level), the above checks arepostponed until navigation moves out of that unit. All outstanding items and recordsare validated together, including the firing of When-Validate-Item andWhen-Validate-Record triggers.You might set a validation unit above item level under one of the following conditions:• Validation involves database references, and you want to postponetraffic until the operator has completed a record (record level).• The application runs in a block-mode environment (block level).Using LOVs for Validation

Page 26: Oracle Form Builder

When you attach an LOV to a text item by setting the LOV property of the item, youcan optionally use the LOV contents to validate data entered in the item.Do this by setting the Validate from List property to Yes for the item. At validationtime, Form Builder then automatically uses the item value as a non case-sensitivesearch string on the LOV contents. The following events then occur, depending on thecircumstances:• If the value in the text item matches one of the values in the first columnof the LOV, validation succeeds, the LOV is not displayed, andprocessing continues normally.• If the item’s value causes a single record to be found in the LOV, but is apartial value of the LOV value, then the full LOV column value isreturned to the item (providing that the item is defined as the return itemin the LOV). The item then passes this validation phase.• If the item value causes multiple records to be found in the LOV, FormBuilder displays the LOV and uses the text item value as the searchcriteria to automatically reduce the list, so that the operator must choose.• If no match is found, then the full LOV contents are displayed to theoperator.Note: Make sure that LOVs you create for validation purposes have the validationcolumn defined first, with a display width greater than 0. You also need to define theReturn Item for the LOV column as the item being validated.For performance reasons, do not use the LOV for Validation property for large LOVs.

Còn tiếp….

Page 27: Oracle Form Builder

19 Navigation

• What is the navigation unit?– Outside the form– Form– Block– Record– Item

• Entering and leaving objects

• What happens if navigation fails?

• Form module– Mouse navigation limit– First navigation data block

• Block– Navigation style– Previous navigation data block– Next navigation data block

• Item– Enabled– Keyboard navigable– Mouse navigate– Previous navigation item– Next navigation item

Page 28: Oracle Form Builder

ExperienceUse default date format (DD-MON-YY) in Query Where

Hot keyFile->Connect Ctrl+JProgram->Complile Module Ctrl+TRun Ctrl+R

Các phím chức năng được sử dụng trong hệ này gồm:

F1 Xem hướng dẫn sử dụng

F3 Lấy dữ liệu tương ứng của truờng hiện tại trong bản ghi trước

F4 Lấy nội dung bản ghi trước gán cho bản ghi mới hiện tại

F6 Thêm một bản ghi

F7 Nhập điều kiện truy vấn

Ctrl+Q Cancel Query

F8 Thực hiện truy vấn dữ liệu

Shift+Down Next Record

F9 Hiển thị danh sách các giá trị có thể chọn cho một trường (trong trường hợp trường đó chỉ được phép lấy giá trị từ một danh sách nhất định)

F10 Ghi dữ liệu thay đổi vào cơ sở dữ liệu (Save)

Shift+F1 Hiển thị lỗI

Shift+F2 Trong chế độ Enter Query, trả về count hits

Shift+F6 Xoá bản ghi hiện tại

TAB Chuyển sang trường tiếp theo

Shift+ATB Chuyển về trường trước