Explore topic-wise InterviewSolutions in .

YES. You can programmatically change an object's named visual attribute SETTING to change the FONT, color, and PATTERN of the object at runtime.

Yes. You can programmatically change an object's named visual attribute setting to change the font, color, and pattern of the object at runtime.

Specifies the named visual attribute used when an item is part of the CURRENT record. Current Record Attribute is frequently used at the block level to display the current ROW in a multi-record If you define an item-level Current Record Attribute, you can display a pre-determined item in a SPECIAL color when it is part of the current record, but you cannot dynamically highlight the current item, as the input focus CHANGES.

Specifies the named visual attribute used when an item is part of the current record. Current Record Attribute is frequently used at the block level to display the current row in a multi-record If you define an item-level Current Record Attribute, you can display a pre-determined item in a special color when it is part of the current record, but you cannot dynamically highlight the current item, as the input focus changes.

When-Mouse-Click.
When-Mouse-DoubleClick.
When-Mouse-Down.
When-Mouse-Enter.
When-Mouse-Leave.
When-Mouse-Move.
When-Mouse-Up.

When-Mouse-Click.
When-Mouse-DoubleClick.
When-Mouse-Down.
When-Mouse-Enter.
When-Mouse-Leave.
When-Mouse-Move.
When-Mouse-Up.

Yes we can port APPLICATIONS across platforms. Consider the form developed in a WINDOWS system. The form would be GENERATED in unix system by USING f45gen my_form.fmb scott/tiger.

Yes we can port applications across platforms. Consider the form developed in a windows system. The form would be generated in unix system by using f45gen my_form.fmb scott/tiger.

When successive forms are LOADED via the CALL_FORM PROCEDURE, the RESULTING module HIERARCHY is known as the call form STACK.

When successive forms are loaded via the CALL_FORM procedure, the resulting module hierarchy is known as the call form stack.

This PROCEDURE INVOKES a method.

Syntax:

Parameters:

• object Is an OLE2 Automation Object.
• method Is a method (procedure) of the OLE2 object.
• list Is the NAME of an argument list assigned to the OLE2.CREATE_ARGLIST FUNCTION.

This procedure invokes a method.

Syntax:

Parameters:

OLE AUTOMATION allows an OLE server application to EXPOSE a set of COMMANDS and functions that can be invoked from an OLE container application. OLE automation provides a WAY for an OLE container application to use the features of an OLE server application to manipulate an OLE object from the OLE container environment. (FORMS_OLE).

OLE automation allows an OLE server application to expose a set of commands and functions that can be invoked from an OLE container application. OLE automation provides a way for an OLE container application to use the features of an OLE server application to manipulate an OLE object from the OLE container environment. (FORMS_OLE).

IDENTIFIES a block as TRANSACTIONAL control block. i.e. non - DATABASE block that ORACLE forms should manage as transactional block.(NON-ORACLE DATASOURCE) default - FALSE.

Identifies a block as transactional control block. i.e. non - database block that oracle forms should manage as transactional block.(NON-ORACLE datasource) default - FALSE.

Specifies whether Oracle Forms should issue savepoints during a SESSION. This property is INCLUDED primarily for applications that will run against non-ORACLE data sources. For applications that will run against ORACLE, use the default setting. Cursor MODE - define cursor STATE across TRANSACTION Open/close.

Specifies whether Oracle Forms should issue savepoints during a session. This property is included primarily for applications that will run against non-ORACLE data sources. For applications that will run against ORACLE, use the default setting. Cursor mode - define cursor state across transaction Open/close.

Yes.

Yes.

It is SIMILAR to C PRECOMPILER DIRECTIVES.

It is similar to C precompiler directives.

Make sure you INCLUDE the name of the DLL in the FORMS45_USEREXIT variable of the ORACLE. INI file, or rename the DLL to F45XTB.DLL. If you rename the DLL to F45XTB.DLL, REPLACE the EXISTING F45XTB. DLL in the ORAWINBIN directory with the NEW F45XTB.DLL.

Make sure you include the name of the DLL in the FORMS45_USEREXIT variable of the ORACLE. INI file, or rename the DLL to F45XTB.DLL. If you rename the DLL to F45XTB.DLL, replace the existing F45XTB. DLL in the ORAWINBIN directory with the new F45XTB.DLL.

The DLL can be created using the Visual C++ / Visual BASIC Tools and then the dll is PUT in the path that is defined the registry.

The dll can be created using the Visual C++ / Visual Basic Tools and then the dll is put in the path that is defined the registry.

YES.

YES.

YES.

YES.

The entries of Pro * C and user exits and the form which simulate the PROC or user_exit are STORED in IAPXTB table in d/b.

The entries of Pro * C and user exits and the form which simulate the proc or user_exit are stored in IAPXTB table in d/b.

YES . You obtain a return VALUE from a foreign function by assigning the return value to an Oracle Forms variable or item. Make sure that the Oracle Forms variable or item is the same data type as the return value from the foreign function.

After assigning an Oracle Forms variable or item value to a PL/SQL variable, pass the PL/SQL variable as a parameter value in the PL/SQL interface of the foreign function. The PL/SQL variable that is passed as a parameter must be a valid PL/SQL data type; it must also be the APPROPRIATE parameter type as DEFINED in the PL/SQL interface.

Yes . You obtain a return value from a foreign function by assigning the return value to an Oracle Forms variable or item. Make sure that the Oracle Forms variable or item is the same data type as the return value from the foreign function.

After assigning an Oracle Forms variable or item value to a PL/SQL variable, pass the PL/SQL variable as a parameter value in the PL/SQL interface of the foreign function. The PL/SQL variable that is passed as a parameter must be a valid PL/SQL data type; it must also be the appropriate parameter type as defined in the PL/SQL interface.

A USER exit is a C subroutine written by you and called by Oracle Forms to do special-purpose processing. You can EMBED SQL STATEMENTS and PL/SQL blocks in your user exit, then precompile it as you WOULD a host program.

When called by an Oracle Forms V3 trigger, the user exit runs, then returns a status code to Oracle Forms. Your exit can display messages on the Oracle Forms status line, get and set field values, do high-speed computations and table lookups, and MANIPULATE Oracle data.

A user exit is a C subroutine written by you and called by Oracle Forms to do special-purpose processing. You can embed SQL statements and PL/SQL blocks in your user exit, then precompile it as you would a host program.

When called by an Oracle Forms V3 trigger, the user exit runs, then returns a status code to Oracle Forms. Your exit can display messages on the Oracle Forms status line, get and set field values, do high-speed computations and table lookups, and manipulate Oracle data.

There are 2 TYPES of canvases CALLED as Content and STACK Canvas. Content canvas is the default and the one that is used mostly for GIVING the base effect. Its like a plate on which we add items and stacked canvas is used for giving 3 DIMENSIONAL effect.

There are 2 types of canvases called as Content and Stack Canvas. Content canvas is the default and the one that is used mostly for giving the base effect. Its like a plate on which we add items and stacked canvas is used for giving 3 dimensional effect.

Yes , OBJECT group can have BLOCK as well as PROGRAM UNITS.

Yes , object group can have block as well as program units.

The When-Timer-Expired TRIGGER can not FIRE during trigger, NAVIGATION, or TRANSACTION PROCESSING.

The When-Timer-Expired trigger can not fire during trigger, navigation, or transaction processing.

forms RUN INSIDE the MDI application window. This property is USEFUL for CALLING a FORM from another one.

forms run inside the MDI application window. This property is useful for calling a form from another one.

When MOUSE Navigate is TRUE (the default), Oracle Forms performs standard navigation to move the focus to the item when the OPERATOR ACTIVATES the item with the mouse. When Mouse Navigate is SET to False, Oracle Forms does not perform navigation (and the resulting validation) to move to the item when an operator activates the item with the mouse.

When Mouse Navigate is True (the default), Oracle Forms performs standard navigation to move the focus to the item when the operator activates the item with the mouse. When Mouse Navigate is set to False, Oracle Forms does not perform navigation (and the resulting validation) to move to the item when an operator activates the item with the mouse.

NO.

NO.

An ALERT is a modal WINDOW that DISPLAYS a MESSAGE notifying operator of some application CONDITION.

An ALERT is a modal window that displays a message notifying operator of some application condition.

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.

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.

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 .

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 .

YES , in LONG RAW DATATYPE.

Yes , in long Raw datatype.

HIDES CHARACTERS that the operator types into the TEXT item. This SETTING is typically used for PASSWORD protection.

Hides characters that the operator types into the text item. This setting is typically used for password protection.

YES , PARTIALLY.

1. PROPERTY CLASS - inheritance property
2. OVERLOADING : procedures and FUNCTIONS.

yes , partially.

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.

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.

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.

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.

• SYSTEM.MESSAGE_LEVEL
• SYSTEM.DATE_THRESHOLD
• SYSTEM.EFFECTIVE_DATE
• SYSTEM.SUPPRESS_WORKING

master delete property

• NON-ISOLATED (DEFAULT)

1. on check delete master
2. on clear DETAILS
3. on populate details

• ISOLATED

1. on clear details
2. on populate details

• CASCADE

1. per-delete
2. on clear details
3. on populate details

master delete property

Yes.

Yes.

%FOUND , %NOTFOUND , %ISOPEN,%ROWCOUNT

%FOUND , %NOTFOUND , %ISOPEN,%ROWCOUNT

VARCHAR2, NUMBER,CHAR , MLSLABEL.

Varchar2, Number,Char , MLSLABEL.

In an indexed CLUSTER, ROWS are STORED together based on their cluster key VALUES . Can not APPLIED for HASH.

In an indexed cluster, rows are stored together based on their cluster key values . Can not applied for HASH.

In EXTENTS .

In extents .

The NUMBER of COLUMNS in a table can RANGE from 1 to 254.

The number of columns in a table can range from 1 to 254.

A pseudocolumn behaves like a table column, but is not actually stored in the table. You can select from pseudocolumns, but you cannot insert, UPDATE, or DELETE their values. This section DESCRIBES these pseudocolumns:

• CURRVAL
• NEXTVAL
• LEVEL
• ROWID
• ROWNUM

A pseudocolumn behaves like a table column, but is not actually stored in the table. You can select from pseudocolumns, but you cannot insert, update, or delete their values. This section describes these pseudocolumns:

YES. With RESPECT to table
ALTER TABLE TABLE
[[ DISABLE all_trigger ]]

Yes. With respect to table
ALTER TABLE TABLE
[[ DISABLE all_trigger ]]

YES. We can delete the duplicate ROWS in the table by using the ROWID.

Yes. We can delete the duplicate rows in the table by using the Rowid.

A post QUERY will fire for EVERY row that is fetched but the pre query will fire only once.

A post query will fire for every row that is fetched but the pre query will fire only once.

Normalisation is the process of organising the tables to remove the redundancy.There are mainly 5 Normalisation RULES.

• 1 Normal Form :: A table is SAID to be in 1st Normal Form when the attributes are ATOMIC.
• 2 Normal Form :: A table is said to be in 2nd Normal Form when all the candidate keys are dependant on the primary key.
• 3rd Normal Form :: A table is said to be third Normal form when it is not dependant transitively.

Normalisation is the process of organising the tables to remove the redundancy.There are mainly 5 Normalisation rules.

CODD Rules DESCRIBE the IDEAL NATURE of a RDBMS. No RDBMS satisfies all the 12 codd rules and Oracle Satisfies 11 of the 12 rules and is the only Rdbms to satisfy the MAXIMUM number of rules.

Codd Rules describe the ideal nature of a RDBMS. No RDBMS satisfies all the 12 codd rules and Oracle Satisfies 11 of the 12 rules and is the only Rdbms to satisfy the maximum number of rules.

When a table is in state of transition it is said to be mutating.

EG :: If a ROW has been deleted then the table is said to be mutating and no OPERATIONS can be DONE on the table except SELECT.

When a table is in state of transition it is said to be mutating.

eg :: If a row has been deleted then the table is said to be mutating and no operations can be done on the table except select.

DELETING a table will not REMOVE the rows from the table but entry is there in the database DICTIONARY and it can be retrieved But truncating a table DELETES it completely and it cannot be retrieved.

Deleting a table will not remove the rows from the table but entry is there in the database dictionary and it can be retrieved But truncating a table deletes it completely and it cannot be retrieved.

Two Phase commit is used in distributed data BASE SYSTEMS. This is useful to maintain the integrity of the database so that all the users see the same values. It contains DML statements or Remote Procedural calls that reference a remote object. There are basically 2 phases in a 2 phase commit.

• PREPARE Phase :: Global coordinator asks PARTICIPANTS to prepare
• Commit Phase :: Commit all participants to coordinator to Prepared, READ only or abort Reply

Two Phase commit is used in distributed data base systems. This is useful to maintain the integrity of the database so that all the users see the same values. It contains DML statements or Remote Procedural calls that reference a remote object. There are basically 2 phases in a 2 phase commit.

Pct Free is USED to DENOTE the percentage of the free space that is to be left when creating a table. SIMILARLY Pct Used is used to denote the percentage of the used space that is to be used when creating a table
eg.:: Pctfree 20, PCTUSED 40

Pct Free is used to denote the percentage of the free space that is to be left when creating a table. Similarly Pct Used is used to denote the percentage of the used space that is to be used when creating a table
eg.:: Pctfree 20, Pctused 40