FORMS TRIGGERS

HOW TO RELATE EVENTS WITH TRIGGERS?

KEY BOARD EVENTS:- THE TRIGGER NAME WILL START WITH KEY-

MOUSE EVENTS:- THE TRIGGER NAME WILL START WITH WHEN-MOUSE-

NAVIGATIONAL EVENTS :- THE TRIGGER NAME WILL START WITH PRE- OR POST-

TRANSACTIONAL EVENTS:- TRIGGER NAME START WITH PRE- OR POST- OR ON- FOLLOWED BY
INSERT , DELETE, UPDATE, COMMIT KEYWORDS.

MASTER DETAIL TRIGGERS :- TRIGGER NAME MUST KEEP EITHER MASTER OR DETAIL KEYWORDS
EX:-
ON-CHECK-DELETE-MASTER
ON-POPULATE-DETAILS

OBJECT-INTERFACE-TRIGGERS:-
THE TRIGGER NAME WILL START WITH WHEN- AND IT WILL KEEP OBJECT NAME/IDENTIFIER LIKE
BLOCK OR ITEM OR WINDOW ETC.

WHEN-BUTTON-PRESSED
WHEN-WINDOW-MAXIMIZED
WHEN-NEW-FORM-INSTANCE

ERROR EVENT- THE TRIGGER IS ON-ERROR

MESSAGE EVENT :- THE TRIGGER IS ON-MESSAGE

WHAT TO WRITE IN TRIGGERS?

A TRIGGER PROGRAM IS NOTHING BUT PL/SQL PROGRAMMING. WITHIN THE TRIGGER WE WRITE
ANONYMOUS BLOCKS AND THERE WE CAN WRITE A COMPLETE PL/SQL CODE. WITHIN THE CODE WE
CAN EVEN CALL PROCEDURES AND FUNCTIONS.

A BUILT -IN IS A PRE-DEFINED METHOD IN THE FORM OF A PROCEDURE OR FUNCTION.

PL/SQL PROGRAMS IN TRIGGERS CAN HAVE THE FOLLOWING STATEMENTS

1. SQL STATEMENTS
2. PL/SQL STATEMENTS
3. FORM SPECIFIC STATEMENTS KNOWN AS (BUILT-INS).

BUILT-INS ARE OF TWO TYPES.

1. RESTRICTED BUILT-INS
2. UNRESTRICTED BUILT-INS

THOSE BUILT-INS THAT CAN CHANGE THE PATH OF CURSOR OR CONTROL NAVIGATION ARE KNOWN
AS RESTRICTED BUILT-INS.

UNRESTRICTED BUILT-INS WILL NOT CHANGE THE PATH OF CURSOR NAVIGATION.

THE FOLLOWING TRIGGERS WILL NOT SUPPORT RESTRICTED BUILT-INS.

1. NAVIGATIONAL TRIGGERS
2. TRANSACTIONAL TRIGGERS
3. ERROR TRIGGERS
4. MESSAGE TRIGGERS

FORM OBJECT RELATED BUILT-INS

1. COMMIT_FORM :- SAVES ALL UNSAVED TRANSACTIONS WITHIN THE FORM

2. EXIT_FORM[(DO_COMMIT|NO_COMMIT|ASK_COMMIT)]
THIS BUILT IN WILL EXIT THE RUN FORM. DEFAULT IS ASK_COMMIT.

3. CLEAR_FORM[(DO_COMMIT|NO_COMMIT|ASK_COMMIT)]
THIS BUILT-IN WILL CLEAR ALL THE BLOCKS WITHIN THE FORM.DEFAULT IS ASK_COMMIT.

4. CALL_FORM(<FORM NAME AND PATH>,[<PARAMETER LIST>])

5. OPEN_FORM(<FORM NAME AND PATH>,[<PARAMETER LIST>])

6. NEW_FORM(<FORM NAME AND PATH>,[<PARAMETER LIST>])

THE ABOVE 3 BUILT-INS ARE USED TO CALL ONE FORM FROM ANOTHER FORM.

BLOCK RELATED BUILT-INS

1. NEXT_BLOCK :- MOVES THE CURSOR NAVIGATION TO THE NEXT BLOCK.
2. PREVIOUS_BLOCK :- MOVES THE CURSOR NAVIGATION TO THE PREVIOUS BLOCK
CLEAR_BLOCK[(DO_COMMIT|NO_COMMIT|ASK_COMMIT)]
CLEARS THE CONTENTS OF A BLOCK DEFAULT MODE IS ASK_COMMIT
4. GO_BLOCK('<BLOCK NAME>')
5. BLOCK_MENU :- DISPLAYS LIST OF ALL THE BLOCKS IN THE FORM MODULE.

QUERY RELATED BUILT-INS

ENTER_QUERY:- PUTS THE APPLICATION IN ENTER QUERY MODE.

EXECUTE_QUERY:- EXECUTES A QUERY THAT HAS BEEN ENTERED
ABORT_QUERY :- CANCELS THE QUERY THAT HAD BEEN PREVIOUSLY ENTERED AND IS CURRENTLY
EXECUTING.

COUNT_QUERY:- RETURNS THE COUNT OF THE RECORDS THAT WILL BE RETURNED BY A QUERY.

RECORD RELATED BUILT-INS

CREATE_RECORD
DELETE_RECORD
CLEAR_RECORD
LOCK_RECORD
DUPLICATE_RECORD
NEXT_RECORD
PREVIOUS_RECORD
FIRST_RECORD
LAST_RECORD
GO_RECORD(<n>)
UP
DOWN
SCROLL_UP
SCROLL_DOWN

ITEM RELATED BUILT-INS

NEXT_ITEM
PREVIOUS_ITEM
CLEAR_ITEM
DUPLICATE_ITEM

BY SETTING KEYBOARD NAVIGATE TO NO AND MOUSE NAVIGATE TO NO WE CAN PREVENT THE

CURSOR OR MOUSE NAVIGATION ON THE BUTTON OBJECT IN THE BUTTON BLOCK. THERE BY THE
CURSOR WILL CONTINUE TO REMAIN IN THE DATABLOCK AND THE METHOD WRITTEN IN THE
BUTTON WILL APPLY TO THE DATA BLOCK.