Navigation between forms in a multiple-form application can occur when the end user navigates with the mouse, or when a form calls one of the following navigational Built-in procedures:
GO_FORM takes one parameter that specifies the name of the target form:
GO_FORM('schedule');
NEXT_FORM and PREVIOUS_FORM navigate to the next or previous form in the same order the forms were opened at runtime:
NEXT_FORM;
PREVIOUS_FORM;
Many triggers fire in response to navigational events, including Pre- and Post- triggers (Pre-Block, Post-Record, etc.) and When-New-Instance triggers (When-New-Block-Instance, When-New-Item-Instance, etc.). When you build a multiple-form application, you should understand how navigation affects trigger processing.
In a multiple-form application, each open form has one item that is the current item for that form. If you use GO_FORM, NEXT_FORM, PREVIOUS_FORM or EXIT_FORM to programmatically initiate navigation to an open form, the target item is always the current item in the target form. For example, when Form A opens and activates Form B, Oracle Forms sets focus to the current item in Form B. If Form B subsequently calls EXIT_FORM or PREVIOUS_FORM, Oracle Forms returns focus to the current item in Form A—in this case, the item that was current when Form A opened Form B.
Keep in mind the following points when navigating between independent forms: