You want to use the Forms Debugger to diagnose a problem with the RAISE_STATUS program unit that is stored in the database.
Forms Builder, you set a breakpoint in the stored code, and then run the Human Resources form in debug mode. You click the Raise_Salaries button, which has a When Button Pressed trigger that calls RAISE_SALARIES.
However, you are unable to see the RAISE_SALARIES procedure when you step through the code, and it does not appear in the stack frame. What could be the reason for this problem?

• A. You are not connected to the database.
• B. You cannot use the Forms Debugger to diagnose problems with stored program units.
• C. The stored program unit was not compiled with the debug information included.
• D. The breakpoint should have been set in the When-Button-Pressed trigger, not in the stored program unit.

View the Exhibit.

The Departments form has form level triggers defined as shown in the Exhibit. You have enabled array DML for the Departments block by setting its DML array size to 5 and setting the Primary Key property of Department id to Yes. You set runtime preferences for Forms Builder to use array processing.
You want to test that array processing is actually occurring, so, as shown in the Exhibit, the On-Update, On-Delete, and on insert triggers have code that:
1. Displays a message to indicate which trigger is firing for which record?
2. Does the thing (either updates, deletes, or inserts)
The other triggers simply display a message, indicating the trigger that is firing.
You run the form from Forms Builder, but from the messages, you can tell that array processing is not occurring. What should you change so that array DML gets implemented?

• A. Set the DML array size to a value of 10 or greater; for array sizes loss than 10, array processing Is inefficient, and so is not performed.
• B. Set the Enforce Primary Key property of the Department block to Yes; it is not enough to just set the Department_Id to be the primary key.
• C. Delete the "On-" triggers; these triggers remove default processing, including array processing.
• D. Use the SYNCHRONIZE built-in after the MESSAGE built-in; otherwise, the message are not displayed until the processing is finished, giving the appearance that array processing is not taking place.

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

You create a Customers form by using wizards. When you test the form, you notice that you cannot the complete name that is displayed in the Customer_Name text item. Which three tools can you use to correct this problem?

• A. Object Library
• B. Layout wizard
• C. Property Palette
• D. Layout Editor
• E. Object Navigator
• F. Data Block wizard