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?

Show Answer Hide Answer

In the Orders form, users often have a need to return to the first record. Because there are many employee records, it may take a long time for them to scroll up to the first record, so you create a button with the label First Record.

When users click the first Record button, you want to display your own custom message instead of the system message "FRM-40100: At first record."

The system message should be displayed in other cases when users attempt to scroll above the first record.

You code the following When-Button-Pressed trigger:

:SYSTEM.mesage_level := '5'

UP;

WHILE FORM_SUCCESS LOOP

UP;

END LOOP;

MESSAGE ('This is the first Order');

The button works perfectly to return to the first record and display your custom message instead of the system message. However, users report that as they continue to use the form after clicking the button, no longer see other helpful messages. For example, the message "FRM 40102: Record must be entered or deleted first" no longer appears when they attempt to scroll past the last record.

How can you resolve this Issue so that all system messages continue to be displayed after the trigger code runs?

Show Answer Hide Answer

The Orders form, whose properties have not been changed from the default, has two non-base table text items to display the sales representative's first and last names.

You want to ensure that entries made in these Items correspond to an existing employee, so you write a When-Validate-Item trigger for the Sales_Rep_First_Name text item:

SELECT LAST_NAME Into :last_name FROM employees

WHERE first_name = :first_name;

EXCEPTION

WHEN NO_DATA_FOUND THEN

MESSAGE ('There is no sales rep by this name');

When you test the form and enter a first name that does not exist in the database, the message that you specified appears, but the cursor goes to the Sales_Rep_Last_Name item. You want the cursor to remain in the Sales_Rep__First Name item until a correct first name is entered.

Also, as you continue to test the form, at times, the cursor does not leave the Sales_Rep_First_Name item after you enter a name, but no error message appears.

Which two things can you do to correct these problems?

Show Answer Hide Answer

Which statement is always true about using OPEN_FORM to open multiple forms in an application?

Show Answer Hide Answer

The Orders form is sometimes run automatically and sometimes run from the Customers form, when it is run from the Customers form, any queries should be restricted to the customer that is currently selected. The Customers form button that runs the Orders form sets a global variable to the current customer ID.

The Orders form has a button labeled Execute Query with the following When-Button Pressed trigger:

DEFAULT_VALUE (NULL, 'GLOBAL.Customer_id');

IF: GLOBAL.customer_id IS NOT NULL

THEN

SET_BLOCK_PROPERTY ('orders', DEFAULT_WHERE, 'orders.customer_id =

' | | :GLOBAL.CUSTOMER_id);

END IF;

EXECUTE_QUERY

You want to duplicate that functionality in a menu item for the Summit menu that is attached To the Orders form.

What changes must you make to the code so that the menu code functions as it does in the form?

Show Answer Hide Answer