View the Exhibit to examine the form.
The text items (Field1, Field2, and Field3) and the button (Check_Values) are in the
CONTROL block. The Mouse Navigate property of the button has been set to No.
The following code has been written in a When-Button-Pressed trigger on the
Check_Values button:
MESSAGE(:field1||' - '||
NAME_IN(:SYSTEM.cursor_item)||' - '||
NAME_IN('SYSTEM.cursor_item'));
With the focus in FIELD1, and the values field1, field2, and field3 in the text items, what message will be displayed when the button is clicked?

• A. CONTROL.FIELD1 - CONTROL.FIELD1 - field1
• B. field1 - field2 - Check Values
• C. field1 - field2 - field3
• D. field1 - field1 - Check Values
• E. CONTROL.FIELD1 - CONTROL.FIELD2 - field3
• F. field1 - field1 - CONTROL.FIELD1
• G. field1 - field1 - field1

You are developing a Human Resources form for HR clerks to insert, update, and delete records from the EMPLOYEES table. When the user commits records, Forms displays the default informative message "FRM-40400: Transaction complete: <n> records applied and saved."
You want to replace that with the message "Records inserted: <n> Records updated: <n>
Records deleted: <n>", where <n> represents the number of records inserted, updated, and deleted.
Which triggers must you create or modify to accomplish this?

• A. On-Message only
• B. Post-Commit and On-Message
• C. Post-Insert, Post-Update, Post-Delete, and On-Message
• D. When-Validate-Record and On-Message
• E. Post-Database-Commit and On-Message

The Orders form has two Record Groups: the SHIP Record Group that was created at design time, and the SOLD Record Group that was created at run time. You are required to write a Program Unit that will delete both Record Groups. Which two statements describe your situation? (Select two.)

• A. You cannot delete Record Group SHIP at run time.
• B. You should delete Record Group SOLD with built-in
  DELETE_GROUP_ROW('SOLD',ALL_ROWS);
• C. You should delete Record Group SHIP with built-in
  DELETE_GROUP_ROW('SHIP',ALL_ROWS);
• D. You should delete Record Group SHIP with built-in DELETE_GROUP('SHIP');
• E. You should delete Record Group SOLD with built-in DELETE_GROUP('SOLD');
• F. You cannot delete Record Group SOLD at run time.

View the Exhibit.
You are coding a trigger (shown in the exhibit) to display the database error that occurs when users encounter the FRM-40505 error about being unable to execute a query. You have created an alert called Query_Alert. For the FRM-40505 error, the trigger should display the database error message in the Query_Alert. For all other errors, the trigger should display default messages on the console message line.
Examine the code for the On-Error trigger. When you attempt to compile this trigger, you receive a compilation error with the message "Error 215 at line 2, column 4: String length constraints must be in range (1..32767)".
What corrections should you make so that the trigger compiles and functions properly?

• A. Change the n variable to a NUMBER data type, replace SHOW_ALERT with
  FIND_ALERT, and change the line beginning with
  SET_ALERT_PROPERTY to
  SET_ALERT_MESSAGE_PROPERTY('Query_Alert',SQLERRM);.
• B. Change the n variable to a NUMBER data type and change SLQERRM to
  DBMS_ERROR_TEXT.
• C. Eliminate the n variable because SHOW_ALERT does not return a value.
• D. Change all occurrences of error_code, error_type, and error_text to message_code, message_type, and message_text.

You designed a standard toolbar to accompany a number of forms so the code behind the buttons is written as generically as possible.
One of the features of this toolbar is that the buttons are synchronized with the state of the form. To achieve this functionality, you wrote generic procedures that are placed in an attached library and are called from various triggers.
For example, if the form is in Enter-Query mode, the procedure set_enter_query_mode will disable the Enter Query button, change the icon for the Exit button, and modify its Tooltip to read "Cancel Query" rather than "Exit".
What must you code to support this approach?

• A. Form-level When-Button-Pressed triggers for each button to call the generic procedures.
  For example, a form-level trigger on the Enter Query
  button has the following code:
  set_enter_query_mode;
• B. Form-level Key triggers that call the generic procedures and item-level When-Button-
  Pressed triggers that call the DO_KEY() built-in. For
  example, Key-Entqry has the following code:
  set_enter_query_mode;
  The When-Button-Pressed trigger on the Enter Query button has the following code:
  DO_KEY('ENTER_QUERY');
• C. Block-level Key triggers that call the generic procedures and item-level When-Button-
  Pressed triggers that call the EXECUTE_TRIGGER()
  built-in and pass the name of the button as a parameter. For example, the Key-Entqry trigger has the following code:
  set_enter_query_mode;
  The When-Button-Pressed trigger on the Enter Query button has the following code:
  EXECUTE_TRIGGER('ENTER_QUERY');
• D. Item-level Key triggers for each button as well as item-level When-Button-Pressed triggers for each button to call the generic procedures. For example, the When-Button-Pressed trigger on the Enter Query button has the following code:
  set_enter_query_mode;
  The Key-Entqry trigger on the Enter-Query button has the following code:
  set_enter_query_mode;