Question: Which triggers are created when master -detail relation?
1) master delete property* NON-ISOLATED (default)
a) on check delete master
b) on clear details
c) on populate details
a) on clear details
b) on populate details
b) on clear details
c) on populate details
Question: which system variables can be set by users?
Question: What are object group?
Answer: An object group is a container for a group of objects. You define an object group when you want to package related objects so you can copy or reference them in another module.
Question: What are referenced objects?
Answer: Referencing allows you to create objects that inherit their functionality and appearance from other objects. Referencing an object is similar to copying an object, except that the resulting reference object maintains a link to its source object. A reference object automatically inherits any changes that have been made to the source object when you open or regenerate the module that contains the reference object.
Question: Can you issue DDL in forms?
Answer: yes, but you have to use FORMS_DDL.
Restrictions: The statement you pass to FORMS_DDL may not contain bind variable
references in the string, but the values of bind variables can be concatenated into the string before passing the result to FORMS_DDL.
Question: What is SECURE property?
Answer: – Hides characters that the operator types into the text item. This setting is typically used for password protection.
Question: What are the types of triggers and how the sequence of firing in text item
Answer: Triggers can be classified as Key Triggers, Mouse Triggers ,Navigational Triggers.
Key Triggers: Key Triggers are fired as a result of Key action.e.g :: Key-next-field, Key-up,Key-Down
Mouse Triggers: Mouse Triggers are fired as a result of the mouse navigation.e.g. When-mouse-button-presed,when-mouse-doubleclicked,etc
Navigational Triggers :: These Triggers are fired as a result of Navigation. E.g : Post-Text-item,Pre-text-item.
We also have event triggers like when –new-form-instance and when-new-block-instance. We cannot call restricted procedures like go_to(‘my_block.first_item’) in the Navigational triggers But can use them in the Key-next-item.
The Difference between Key-next and Post-Text is an very important question. The key-next is fired as a result of the key action while the post text is fired as a result of the mouse movement. Key next will not fire unless there is a key event.
The sequence of firing in a text item are as follows::
a) pre – text
b) when new item
d) when validate
e) post text
Question: Can you store pictures in database? How?
Answer: Yes, in long raw datatype.
Question: What are property classes? Can property classes have trigger?
Answer: Property class inheritance is a powerful feature that allows you to quickly define objects that conform to your own interface and functionality standards. Property classes also allow you to make global changes to applications quickly. By simply changing the definition of a property class, you can change the definition
of all objects that inherit properties from that class. Yes. All type of triggers.
Question: If you have property class attached to an item and you have same trigger written for the item. Which will fire first?
Answer: Item level trigger fires , If item level trigger fires, property level trigger won’t fire. Triggers at the lowest level are always given the first preference. The item level trigger fires first and then the block and then the Form level trigger.
Question: What are record groups? Can record groups created at run-time?
Answer: A record group is an internal Oracle Forms data structure that has a column/row framework similar to a database table. However, unlike database tables, record groups are separate objects that belong to the form module in which they are defined. A record group can have an unlimited number of columns of type CHAR, LONG, NUMBER, or DATE provided that the total number of columns does not exceed 64K. Record group column names cannot exceed 30 characters.Programmatically, record groups can be used whenever the functionality offered by a two-dimensional array of multiple data types is desirable.
TYPES OF RECORD GROUP:
Query Record Group A query record group is a record group that has an associated SELECT statement.
The columns in a query record group derive their default names, data types, and lengths from the database columns referenced in the SELECT statement. The records in a query record group are the rows retrieved by the query associated with that record group.
Non-query Record Group: A non-query record group is a group that does not have an associated query, but whose structure and values can be modified programmatically at runtime.
Static Record Group: A static record group is not associated with a query; rather, you define its structure and row values at design time, and they remain fixed at runtime.