Description
Modules consist of one or more procedures that are executed one after the other in a particular sequence. The sequence in which the procedures are executed is called the control flow and is important because it decides how the application should behave and affects the outcome of results. For instance, it is important that a search be executedr before a report so that the results that appear in the report are the records filtered by the search.

By default, the sequence of events is defined by the order of the procedures as they appear in the procedure list for the module. The first procedure that appears in the list is always the first procedure that is executed. If the first procedure does not define a procedure to jump to aferwards, then by default, the second procedure in the list will be executed, and so on.

Some procedure allow you to define procedures to go to on certain conditions. For instance, the search procedure allows you to define a procedure to jump to if no matching records found by the search, and another procedure to go to if records are found. This is useful for presenting the user with two different screens, one for each outcome. If you select a procedure to jump to on an event, then execution will move to that procedure and proceed from there. If no procedure is defined, then the next procedure in the list will be executed.

The jump procedure allows you to define a procedure to jump to when this procedure is executed. For instance, if you want to return to the first procedure after your last procedure has been executed, then put a jump procedure at the end, and select the first procedure as the procedure to which to jump.

See Also
Procedures