In the Orders form, you create a button in the CONTROL block to send the input focus to the INVENTORIES block and cause it to be replaced.
You write this code in a When-Button-Pressed trigger.
GO_BLOCK(‘Inventories’);
EXECUTE_QUERY;
What happens when you test the form?
A.
The form will not compile because the block name must be uppercase.
B.
The form compiles, but clicking the button causes a Navigation Trap to be encountered.
You must revise the code to avoid such a trap.
C.
The form compiles and runs as required.
Focus moves to the INVENTORIES block, and it is queried automatically when the button is clicked.
D.
The form compiles and focus moves to the INVENTORIES block.
But because the internal cursor is still in the CONTROL block, the query is attempted against the wrong block.
E.
The form compiles, but clicking the button causes an error message to appear.
GO_BLOCK() is a restricted procedure and cannot be called from any "When" triggers.
F.
The form compiles, but clicking the button leaves the focus in the original block, which is then queried.
This could have been prevented if you had coded a check for FORM_SUCCESS after the GO_BLOC();