You do not want users to execute queries while in the Order_Items block, so you write the following key-Exeqry trigger for the Order_Items block: GO_BLOCK('orders'); EXECUTE_QUERY; This works fine…

Question

Options

• ASet the Fire in Enter-Query Mode property of the Key-Exeqry trigger to Yes.
• BAdd the following as the first of the key-Exqry trigger to Yes.
• CDelete the Key-Exqry trigger and define the following Key-Entqry trigger for the Order_Items block:
• DDelete the Key-Exqry trigger and define the following Key-Entqry trigger for the Order_Items block:
• EChange the key-Exqry trigger to:
• FChange the Key-Exeqry trigger to:
• GYou cannot change this behavior, but you should use the On-Message trigger to display a more meaningful

• B
  4% (1)
• C
  78% (18)
• D
  4% (1)
• F
  13% (3)

Explanation

Note: You can use system variables and built-ins to obtain information about queries. Using SYSTEM.mode Use the SYSTEM.mode system variable to obtain the form mode. The three values are NORMAL , ENTER_QUERY , and QUERY. NORMAL Indicates that the form is currently in normal processing mode. ENTER-QUERY Indicates that the form is currently in Enter Query mode. QUERY Indicates that the form is currently in fetch processing mode, meaning that a query is currently being processed. Note 1: ENTER_QUERY procedure Clears the current block and creates a sample record. Operators can then specify query conditions before executing the query with a menu or button command.If there are changes to commit, the Forms Builder prompts the operator to commit them before continuing ENTER- QUERY processing Note 2: EXECUTE_QUERY procedure Clears the current block, opens a query, and fetches anumber of selected records. If there are changes tocommit, Forms Builder prompts the operator to committhem before continuing EXECUTE-QUERYprocessin

No community discussion yet for this question.