Re: parameterübergabe mit call_form

hi!

es gibt in forms gaaaanz rechts einen menüpunkt, der nennt sich "hilfe" oder "help", und da hab ich erstaunlicherweise folgendes gefunden:

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:

n GO_FORM

n NEXT_FORM

n PREVIOUS_FORM

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, Form Builder sets focus to the current item in Form B. If Form B subsequently calls EXIT_FORM or PREVIOUS_FORM, Form Builder 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:

n No validation occurs in the starting form. It is possible to navigate out of a field that is currently invalid provided that the target field is in a different form. Upon returning to the starting form and attempting to navigate within that form, normal validation is enforced.

n With a few exceptions, no triggers fire. The only exceptions are When-Window-Deactivated (fires in the initiating form), and When-Window-Activated (fires in the target form). The Pre-, Post- and When-New-Instance triggers do not fire when navigating between forms.

When an end user uses the mouse to navigate from Form A to Form B, the target item can be either the current item in Form B or another item in Form B.
If the end user clicks:

n the current item in Form B, no triggers fire

n any other item in Form B, triggers fire that normally would fire when navigation occurs from the current item in Form B to the target item, and validation occurs as required. In other words, form processing proceeds exactly as it would if the end user were navigating from the current item in Form B to the target item, without regard to any external forms.