There are two buttons on a form: Button1 and Button2. When you make a change in the appearance of Button1, you want the appearance of Button2 to change automatically.
How can you implement this?
The Products.fmb module has one content canvas, which displays information about products sold by your company.
You increase the canvas display area by creating an overlay canvas to enable product images to be displayed on request. At run time, however, the overlay canvas is never displayed; users complain that there is only a brief flash on their screen.
How do you correct this?
You are developing a form that servers as a front end to access the Order Entry application. Within the form you want to store the usernames of those users who have permissions to run the application. This information
is accessed when the form starts up to determine if the user is authorized. The list of usernames is not stored in the database and should not be visible to users.
How will you store this information?
The Orders form has two base table blocks and a control block. There is an Execute Query button in the control block with the following When-Button-Pressed trigger:
DO_KEY('execute_query);
A user navigates to the Order Items block and clicks Execute Query. The query does not execute, but instead returns error FRM-41003: "This function cannot be performed here".
What can you do to fix this error?
There is a requirement to invoke the Orders form from the Customers form. Your colleagues offer some suggestions about which built-in to use and their reasons for the choice.
Which suggestion names a built-in that will meet the requirement and offers a correct reason?
You have created a default master-detail form, and you need to have a query executed automatically when the form starts. Identify the trigger that is the best place for this code:
DO_KEY('EXECUTE_QUERY');
When called from the Customers form, the Orders form enables order entry clerks to place new orders for the current customer using the customer ID passed from the Customer form as a parameter.
If clerks decide to cancel a new record without entering further information, they do not want to be required to clear the record.
You must assign the value of the parameter to the Customer_Id item in each new record of the Orders from with this code:
:orders.customer_id :=:parameter.customer_id;
Where should you place this code to meet the requirements of the order entry clerks and also to ensure that each new order has the correct customer ID?
You are running a multiple-form application. The Customers form invoked the Orders form. When the Orders form launches, it displays orders for only the active customer from the Customers form.
Forms exchange data with the :GLOBAL.CUSTOMER_ID variable.
The Orders form should be restricted to orders for the current customer only the first time a query is issued after invoking the Orders form.
Which built-in helps you to do this by setting the ONETIME_WHERE property to refer dynamically to the
GLOBAL.CUSTOMER_ID?
You need to restrict access to a form. Access must be limited to a particular times of day and to certain authorized users.
You write a procedure (get_authorization) in the form that checks the username of the person logging in and validates the time of day. If the person is not authorized to use the form at that time, the following code is
executed: ...
MESSAGE
('You are not authorized to access the form at this time');
RAISE FORM_TRIGGER_FAILURE;
What is the best trigger from which to call this procedure? Why?