You have a text item in your form named Object1. You want to create Object2 as an exact duplicate of Object1. You want to be able to change the properties of Object2. However if you change Object1, you do not want Object2 to change.
Which method of reusing Object1 would be best for these requirements?

• A. Copying Object1
• B. Putting Object1 in an Object library
• C. Referencing Object1 in a PL/SQL library
• D. Creating a property class from Object1
• E. Subclassing Object1

The Orders form has three blocks: Orders, Orders_Items, and inventories. It also has a button labeled Next Block with a When-Pressed trigger.
IF :SYSTEM.cursor_block = 'orders' THEN
GO_BLOCK('order_items');
ELSIF :SYSTEM.cursor_block = 'order_items' THEN
GO_BLOCK('inventories');
ELSIF :SYSTEM.cursor_block = 'inventories' THEN
GO_BLOCK ('orders');
END IF;
The button is not functioning correctly; it does not cause navigation to occur. What must you do to fix the issue?

• A. instead of naming the block to navigate to, replace the GO_BLOCK built-in with NEXT_BLOCK
• B. Change the block names to uppercase in the condition (IF ...THEN) statements.
• C. Change all occurrences of :SYSTEM.cursor_block to :SYSTEM.trigger_block.
• D. Use system variables in the GO_BLOCK statements.
• E. Move the code to a PL/SQL program unit.
• F. Change the block names to uppercase in the GO_BLOCK statements.

You are using a PL/SQL program unit in the Orders form to display an image for the selected product in the Order Items block. The code is called from several different triggers in the form. The code (with line numbers added) is:
1. PROCEDURE get_image IS
2. Product_image_id ITEM := FIND_ITEM ('control.product_image');
3. Filename VARCHAR2(250);
4. BEGIN
5. Filename := TO_CHAR(:order_items.product_id) | | '.jpg';
6. READ_IMAGE_FILE (filename, 'jpeg', product_image_id);
7. END;
Management wants all codes to be in PL/SQL libraries to facilitate reuse. You create a PL/SQL library and drag the program unit from the orders form to the Program Units node of the library. You then delete the program unit from the Orders form.
What three things must you do to compile the PL/SQL library and to use the code in the Orders form?

• A. Generate the a .plx file.
• B. Attach the library to the orders form.
• C. Change product_id to an in parameter and filename to an OUT parameter.
• D. Delete the BEGIN and END statements (lines 4 and 7).
• E. Change the way the program unit is called in the Orders form.
• F. Change line 5 to:
  filename := to_char(name_in 'order_items.product_id' )) | | '.jpg';.
• G. insert the RELEASE keyword between lines 1 and 2.
• H. Save the library.

Users do not want to see the "Working" message while a long query completes.
You are designing a form with a query that takes o long time to execute. What can you do to stop the "Working" message from appearing?

• A. You do not need to do anything, the default behavior of Forms is to display the
  "Working" message only if you add code to do so.
• B. Before the line of code that executes the query, add the line:
  :SYSTEM.SUPPRESS_WORKING : = 'TRUE';
• C. Before the line of code that executes the query, add the line:
  :SYSTEM.MESSAGE_LEVEL := '10';
• D. Use the SET_APPLICATION_PROPERTY built-in to set the message level in a When- New-Form-instance trigger.

When tabbing through items in the Employees form, users should not be able to navigate to the Salary text item. If they need to update the item, they will have to explicitly navigate to it by using the mouse.
Which property setting accomplishes this requirement?

• A. Enabled = Yes; Keyboard Navigable = No
• B. Enabled = Yes; Keyboard Navigable = Yes
• C. Enabled = No; Keyboard Navigable = Yes
• D. Enabled = No; Keyboard Navigable = No
• E. Automatic Skip = Yes