The Orders form is a master-detail form in which ORDERS is a single-record master block and ORDER_ITEMS is a multi record detail block.
During testing of the Orders form, users have complained about the behavior of Enter-Query mode. In the form they are testing, they are unable to navigate out of the current block while they are in Enter-Query mode.
However, they would like to be able to carry out the following procedure:
1. Press [Enter Query] while in the master block.
2. Enter some search criteria.
3. Navigate to the detail block.
4. Enter more search criteria (while the form is still in Enter-Query mode).
5. Press [Execute Query] to have the criteria applied to both blocks at once.
How can you provide the requested functionality?
A.
The requested functionality is the default behavior.
You simply need to remove or rewrite the triggers you wrote that “broke” the form.
B.
Use a Key-Entqry trigger on the master block to redirect the focus to the detail block after the search criteria have been entered in the master block.
C.
You cannot perform the requested operation with a master-detail form.
The restriction on navigating out of the current block during Enter-Query mode cannot be circumvented�.
D.
Use a Key-Exeqry trigger on both the master and detail blocks to call a centralized procedure and have the procedure handle the navigation.
E.
Use a Key-Nxtblk trigger on the ORDERS block to cause navigation to the ORDER_ITEMS block.
This will work because Key triggers can fire in Enter-Query mode and call restricted built-ins such as GO_BLOCK().
F.
Use a combination of Key-Entqry and Key-Exeqry triggers at form level to call generically written procedures to test where the current focus is and set global variables that a form-level Key-Nxtblk trigger can use to redirect the focus.