Explore topic-wise InterviewSolutions in .

SIX EVEN support an APPLICATION.

open(),close(),connection BEGIN(),CONNECTIONS(),idle(),system error().

Six even support an application.

open(),close(),connection begin(),connections(),idle(),system error().

No,But you need`multiple INHERITANCE then you can INHERIT one object from other and You make one object as USEROBJECT and then use this userobject INHERITED object.

No,But you need`multiple inheritance then you can inherit one object from other and You make one object as userobject and then use this userobject inherited object.

TWO TYPES of INHERITANCE: SINGLE Inheritance and Multi-level Inheritance.

Two types of Inheritance: Single Inheritance and Multi-level Inheritance.

• Application (debugging, error MESSAGE, SECURITY)
• Data window (FILTER, LINKAGE, print PREVIEW, resize, sorting)
• Window (menu, resize, file, metaclass)

• CHECK library search PATH in DEVELOPMENT, required DLL’s, PBL’s in runtime etc
• If PFC is used, check that the PB version is exactly the same as PFC version, i.e. 5.0.04 etc
• Use DLL tracking UTILITY to check executables DLL list
• Enabling the PB Debug Tracing information and find the last line of code that executed prior to the GPF.

It is a feature that enables you to build windows, user objects, and menus that are derived from existing objects. When you change an ancestor OBJECT, the changes are reflected in all the descendants and the descendant inherits the ancestor's scripts.

Two main features to be noted here are:

1. Descendant objects - In PB, an object class can be inherited from another class. The inherited or descendent object has all the instance variables, events, and functions of the ancestor. You can augment the descendant by adding more variables, events, and functions. If you change the ancestor, even after editing the descendant, the descendant incorporates the changes.
2. Instantiating - When you instantiate a descendent object, PowerBuilder also INSTANTIATES all its ancestor classes. You do not have programmatic ACCESS to these ancestor instances, except in a few limited ways, such as when you use the scope OPERATOR to access an ancestor VERSION of a function or event script.

It is a feature that enables you to build windows, user objects, and menus that are derived from existing objects. When you change an ancestor object, the changes are reflected in all the descendants and the descendant inherits the ancestor's scripts.

Two main features to be noted here are:

Enumerated data types are specific to POWER Script. They are used as arguments in functions and also to specify the properties of an object or control. A variable of one of the enumerated data types can be ASSIGNED a fixed set of VALUES. For example, the enumerated data TYPE Alignment, which specifies the alignment of text, can be assigned one of the following three values. Center! Left!, and Right.

For example:mle_edit.Alignment=Right.

Enumerated data types are specific to Power Script. They are used as arguments in functions and also to specify the properties of an object or control. A variable of one of the enumerated data types can be assigned a fixed set of values. For example, the enumerated data type Alignment, which specifies the alignment of text, can be assigned one of the following three values. Center! Left!, and Right.

For example:mle_edit.Alignment=Right.

When you embed an object it is SAVED as part of the OLE container object i.e. any changes to the actual object will not reflect in the embedded object. In case of Linking the original object resides where it was and link information is STORED in the OLE container object i.e. any changes to the actual object will reflect in the OLE container object. OCX is an OLE CONTROL that IMPLEMENTS the component-based ARCHITECTURE.

When you embed an object it is saved as part of the OLE container object i.e. any changes to the actual object will not reflect in the embedded object. In case of Linking the original object resides where it was and link information is stored in the OLE container object i.e. any changes to the actual object will reflect in the OLE container object. OCX is an OLE control that implements the component-based architecture.

DDE stands for dynamic data exchange by MEANS of which two APPLICATIONS can TALK to each other and exchange data between them. Examples are RemoteExec & Remote SEND. A PB window has DDE events associated with it.

DDE stands for dynamic data exchange by means of which two applications can talk to each other and exchange data between them. Examples are RemoteExec & Remote Send. A PB window has DDE events associated with it.

Given below are the SQL statements in scripts that are possible with Sybase ASE:

• Transaction Management statements – CONNECT, COMMIT, ROLLBACK and DISCONNECT are used to manage transactions in ASE. If a trigger fails, then a RAISEERROR should be issued in the trigger and not ROLLBACK. PB has got a DBMS SPECIFIC return code (SQLDBCode = -1) WITHIN the transaction object which can be used to throw messages to the user.
• Non-cursor statements – INSERT/UPDATE/DELETE/SELECT.
• Cursor statements – the user can retrieve ( declare, open, fetch & close cursors) and issue update( update & delete cursors).
• DB Stored Procedures – they can be used for retrieve, update or both. To execute DDL statements the AutoCommit must be SET to TRUE (1), but if it is TRUE, ROLLBACK cannot be issued, hence after completion of the DDL operation it must be set back to FALSE.

Given below are the SQL statements in scripts that are possible with Sybase ASE:

Export the window as a SRW and look for the menu name in the FILE. Once FOUND the menu can be created again and linked to the SOURCE window.

Export the window as a SRW and look for the menu name in the file. Once found the menu can be created again and linked to the source window.

Parent refers to the PB object where the current object is placed. For example parent in a command BUTTON’s script will refer to the WINDOW in which the command button is placed. Parentwindow is used to refer to the window for which the current MENU is attached.

Parent refers to the PB object where the current object is placed. For example parent in a command button’s script will refer to the window in which the command button is placed. Parentwindow is used to refer to the window for which the current menu is attached.

This, PARENT, parentwindow & SUPER.

This, parent, parentwindow & super.

USE the Dbhandle () FUNCTION.

Use the Dbhandle () function.

The former EXECUTES the specified event’s SCRIPT RIGHT away while the latter posts the request in the operating system’s MESSAGE queue.

The former executes the specified event’s script right away while the latter posts the request in the operating system’s message queue.

When you OPEN a window in a MDI frame using opensheet () or opensheetwithparm () the window gets the sheet properties IRRESPECTIVE of the window type. If a RESPONSE window is opened using the above functions the window will behave like any other sheet having MAXIMISE, minimize, CLOSE controls etc.

When you open a window in a MDI frame using opensheet () or opensheetwithparm () the window gets the sheet properties irrespective of the window type. If a response window is opened using the above functions the window will behave like any other sheet having maximise, minimize, close controls etc.

They are main, popup; child, RESPONSE, MDI frame, and MDI frame with microhelp.

They are main, popup; child, response, MDI frame, and MDI frame with microhelp.

It can be DONE by GOING to the update properties in the DW by selecting Rows/Update properties from the MENU in the design mode in the DW PAINTER. The tables to be updated can be selected.

It can be done by going to the update properties in the DW by selecting Rows/Update properties from the menu in the design mode in the DW painter. The tables to be updated can be selected.

SQLPreview ().

SQLPreview ().

A DW can retrieve only one RESULT set at a time. To retrieve other result sets, you can change the result set number EITHER by modify () or using object notation MAKING sure the number of columns and data types match the existing DW DEFINITION.

A DW can retrieve only one result set at a time. To retrieve other result sets, you can change the result set number either by modify () or using object notation making sure the number of columns and data types match the existing DW definition.

WRITE CODE in the retrievrow () EVENT and also set the asynch attibute in the DBParm PROPERTY in the transaction OBJECT.

Write code in the retrievrow () event and also set the asynch attibute in the DBParm property in the transaction object.

The FORMER is defined as part of the SELECT STATEMENT, (for example sum, avg etc) WHOSE VALUES are calculated by the database, while in the latter the PB client CALCULATES the values. If it is a fat client then computed fields are recommended, else for thin clients it is computed column.

The former is defined as part of the SELECT statement, (for example sum, avg etc) whose values are calculated by the database, while in the latter the PB client calculates the values. If it is a fat client then computed fields are recommended, else for thin clients it is computed column.

It occurs when a USER updates the data before you update it. PB detects it when you include the timestamp column in the DW or use “key and updateable columns” in the WHERE CLAUSE. The solution to the problem would be to use the reselect row () function to reselect the row that caused the error and GET the latest values for the error row and update the DB again.

It occurs when a user updates the data before you update it. PB detects it when you include the timestamp column in the DW or use “key and updateable columns” in the WHERE clause. The solution to the problem would be to use the reselect row () function to reselect the row that caused the error and get the latest values for the error row and update the DB again.

If the data in a column has changed, it checks for the correctness of the value (both data type and data value) in the PRIMARY buffer. Wrong data type or data value will trigger the ItemError () EVENT. If the data is CORRECT it triggers ITEM changed () event, which if it RETURNS ZERO, triggers itemfocuschanged () event.

If the data in a column has changed, it checks for the correctness of the value (both data type and data value) in the primary buffer. Wrong data type or data value will trigger the ItemError () event. If the data is correct it triggers item changed () event, which if it returns ZERO, triggers itemfocuschanged () event.

You can COPY the selected rows to a data store or a HIDDEN DW control USING rowscopy () and PRINT the data store or hidden DW control.

You can copy the selected rows to a data store or a hidden DW control using rowscopy () and print the data store or hidden DW control.

Yes, it can be USED when your DWs data source CONTAINS a SELECT STATEMENT with an IN clause.

Yes, it can be used when your DWs data source contains a Select statement with an IN clause.

It can be done by linking the DW CONTROL to MODIFY () FUNCTION or using “. OBJECT” notation.

It can be done by linking the DW control to modify () function or using “. Object” notation.

Uos are custom visual objects that you can BUILD to supplement standard PB objects. UOs can request/display information and respond to mouse or keyboard actions and create a tab page UO.

Visual UO – a reusable control/set of controls. For example a set of buttons to function as a unit having scripts associated with them for standard processing.

THREE types are:

1. Standard – inherited from a specific visual control. For example command button/checkbox etc.
2. Custom - inherited from the user OBJECT system class. You can include many controls in the UO and write scripts for these EVENTS.
3. External - it is a UO that displays a visual control defined in a DLL.

Class UO – they consist of properties, FUNCTIONS, and events with no visual components.

1. Standard – inherited from a NV PB object such as a transaction/error object, which can have instance variables and functions.
2. Custom – an object of your own design for which you define variables, events and functions in order to encapsulate application-specific programming in an object.

Uos are custom visual objects that you can build to supplement standard PB objects. UOs can request/display information and respond to mouse or keyboard actions and create a tab page UO.

Visual UO – a reusable control/set of controls. For example a set of buttons to function as a unit having scripts associated with them for standard processing.

Three types are:

Class UO – they consist of properties, functions, and events with no visual components.

It is a feature in PB where a function is defined with the same name as ANOTHER. The two FUNCTIONS may differ in the number of arguments and also the TYPE of arguments. An example is the Messagebox () function.

It is a feature in PB where a function is defined with the same name as another. The two functions may differ in the number of arguments and also the type of arguments. An example is the Messagebox () function.

Only this FUNCTION should be used for composite presentation styles acting as containers for other DW objects. If SETTRANS () is used with each DW in a composite DW then disconnect does not occur until PB session ends. It should be used only for pure RETRIEVAL when DB locks need not be held on tables in other words update () functions are not used.

Only this function should be used for composite presentation styles acting as containers for other DW objects. If settrans () is used with each DW in a composite DW then disconnect does not occur until PB session ends. It should be used only for pure retrieval when DB locks need not be held on tables in other words update () functions are not used.

An important consideration is the usage of COMMIT/CONNECT statements to maximize performance and limit LOCKING and resource use.

Two design CONSIDERATIONS that should be taken care are:

Long running connections – if these are NOT ACCEPTABLE then the application should connect to the database only when necessary. If acceptable then COMMITs should be issued as OFTEN as possible so that the changes do in fact occur. More importantly COMMITs should be issued to release any locks placed on DB entities as a result of statements executed during the transaction.

Settrans/Settransobject function – if the application functionality requires connections to be kept open and issue periodic COMMITs then Settransobject () should be used or use Settrans () for many short-lived transactions.

An important consideration is the usage of COMMIT/CONNECT statements to maximize performance and limit locking and resource use.

Two design considerations that should be taken care are:

Long running connections – if these are NOT acceptable then the application should connect to the database only when necessary. If acceptable then COMMITs should be issued as often as possible so that the changes do in fact occur. More importantly COMMITs should be issued to release any locks placed on DB entities as a result of statements executed during the transaction.

Settrans/Settransobject function – if the application functionality requires connections to be kept open and issue periodic COMMITs then Settransobject () should be used or use Settrans () for many short-lived transactions.

N-Up: two or more ROWS of data displayed next to each other across the page. It is useful for periodic data such as data for each day/week or each month in the quarter.

CrossTab: provides a data summary in a row and COLUMN format. Data to be selected from one or more tables, DW cannot be external. Crosstab functions can be used for filters, validation RULES or COMPUTED fields.

Composite: - it consists of one or more nested reports. It also serves as a container for other reports and has no data source of its own. The user can specify one DW object to be shown on screen, as many reports as the number of DW OBJECTS can be viewed on screen based on the retrieval arguments specified by the user.

N-Up: two or more rows of data displayed next to each other across the page. It is useful for periodic data such as data for each day/week or each month in the quarter.

CrossTab: provides a data summary in a row and column format. Data to be selected from one or more tables, DW cannot be external. Crosstab functions can be used for filters, validation rules or computed fields.

Composite: - it consists of one or more nested reports. It also serves as a container for other reports and has no data source of its own. The user can specify one DW object to be shown on screen, as many reports as the number of DW objects can be viewed on screen based on the retrieval arguments specified by the user.

• Instance variables are created when the object is created and destroyed when the object is destroyed while a shared variable is created when the FIRST instance of the object is created and is destroyed when the application is closed.
• The VALUE of an instance variable in each instance is independent of its value in other INSTANCES while changing the value of a shared variable in ONE instance will affect other instances.

• By Value – a COPY of the variable is passed. Any changes to the value of the variable will affect the copy only, the original variable in the calling script is not affected.
• By REFERENCE – a pointer to the variable is passed to the function/event. Any changes affect the original variable in the calling script.
• READ-ONLY – a copy of the variable TREATED as a CONSTANT is available to the function/event.

• PB 8 supports both ANSI and double-byte character sets (DBCS); any PB8 application runs in a DBCS environment. In a DBCS environment 1 character = 2 bytes as opposed to 1 byte in an ANSI environment. For example we MAY need to change the width of a column of type char (40) to char (80).
• The wide version of the Len () function (called Lenw ()) should be used since the former returns the number of bytes while the latter returns the number of characters.
• PowerBuilder can access UNICODE DATA in an ASE 12.5 Unicode database or in Unicode columns in ASE 12.5. PowerBuilder converts between double-byte character SET (DBCS) data and Unicode automatically, provided that the Locale parameter is set with DBCS values. For example, the Locale DBParm should be set to chs or cht.

A dropdown DW is a DWChild. For example a DW object that POPULATES a COLUMN having the dropdown DW EDIT style is a DWChild object. It does not have any EVENTS ASSOCIATED with it.

A dropdown DW is a DWChild. For example a DW object that populates a column having the dropdown DW edit style is a DWChild object. It does not have any events associated with it.

The FOLLOWING steps are involved in the process:

• Use. modify/.object NOTATION to MAKE ONE table updateable
• SET the primary keys for the table
• Perform DW_1 update with FALSE argument for the reset option in the Update() FUNCTION
• After © is successful, make 2nd table updateable and 1st table not updateable
• Next call update() with TRUE argument for the the reset option in the Update() function
• COMMIT/ROLLBACK depending on success or failure.

The following steps are involved in the process:

When the Auto Commit property is set to FALSE (default) or 0, PB issues SQL statements inside the scope of a transaction. 1(TRUE) implies statements outside the scope of a transaction (for example when your application requires creating TEMPORARY TABLES).

• If you want to execute STORED procedures containing DDL (CREATE, ALTER, DROP etc) statements, then Auto Commit = TRUE.
• If Auto Commit = TRUE, then rollback cannot be issued, it should be set to FALSE after completing the DDL operation.

When Auto Commit is set from FALSE to TRUE, then PB issues a COMMIT STATEMENT by default.

When the Auto Commit property is set to FALSE (default) or 0, PB issues SQL statements inside the scope of a transaction. 1(TRUE) implies statements outside the scope of a transaction (for example when your application requires creating temporary tables).

When Auto Commit is set from FALSE to TRUE, then PB issues a COMMIT statement by default.

• Quick Select – Used when DATA comes from one or more tables linked by a foreign key.
• SQL Select – In ADDITION to above grouping & computed columns can be specified
• External – the data can be imported from a FLAT file or populated from the CODE. ( for example using setitem() methods)
• Query – used when the data source (SQL statement) is saved in a query OBJECT defined in the query painter.
• Stored Procedure

It can be used if the number of connections to theDB are LIMITED and ALSO for pure retrieval when COMMIT & ROLLBACK are not application PRIORITIES.

It can be used if the number of connections to theDB are limited and also for pure retrieval when COMMIT & ROLLBACK are not application priorities.

PFC is a combination of reusable and extendible classes and framework.

The 8 LIBRARIES are:

• pfcmain.pbl – basic services
• pfcapsrv.pbl – application
• pfcdwsrv.pbl – data window
• pfcw srv.pbl – window

The 4 extension layer class libraries are pfemain.pbl, pfeapsrv.pbl, pfedwsrv.pbl & knownsrv.pbl. 2 more security RELATED libraries (with no extension layers) are pfcsecad.pbl & pfcsecsc.pbl.

PFC is a combination of reusable and extendible classes and framework.

The 8 libraries are:

The 4 extension layer class libraries are pfemain.pbl, pfeapsrv.pbl, pfedwsrv.pbl & knownsrv.pbl. 2 more security related libraries (with no extension layers) are pfcsecad.pbl & pfcsecsc.pbl.

It specifies the PARAMETERS required to connect to an ODBC data source. PowerBuilder uses these parameters to connect to the database. The SYNTAX is

Connect String = 'DSN = data_source_name; {UID = user_Id; PWD = password; driver_specific_parameters}'

PowerBuilder generates the Connect String automatically when you DEFINE an ODBC data source and copies it to the DBParm box in the Database Profile Set-up dialog box. This happens before you connect to the data source in PowerBuilder.

It specifies the parameters required to connect to an ODBC data source. PowerBuilder uses these parameters to connect to the database. The syntax is

Connect String = 'DSN = data_source_name; {UID = user_Id; PWD = password; driver_specific_parameters}'

PowerBuilder generates the Connect String automatically when you define an ODBC data source and copies it to the DBParm box in the Database Profile Set-up dialog box. This happens before you connect to the data source in PowerBuilder.

• APPLICATION – any front end/GUI from where ODBC calls are made.
• Driver Manager – it is a DLL that CONTROLS loading of appropriate drivers to connect to DBMS. When an ODBC call is made, it scans the *.ini files to determine which driver to use.
• Driver – it is the heart of ODBC that takes CARE of N/W protocols to connect to the data source; it also submits SQL statements to the data source.
• RDBMS – an ASCII file containing information such as DBMS name, login/password etc.

ODBC takes care of LOCATING the Sybase/SQL server address on the network by reading the win.ini/sql.ini files.

ODBC takes care of locating the Sybase/SQL server address on the network by reading the win.ini/sql.ini files.

While using settrans () the user need not specify an explicit CONNECT or DISCONNECT statement in the script since PB internally calls them whenever required. As PART of internal transaction management of DW controls, when the DW needs to access the DB, the DW control issues an internal CONNECT, performs data access and then issues an internal DISCONNECT.

Settransobject () is used when the user goes for a separate transaction object (example SQLCA) or creates a separate one in the script.

The sequences of statements are as follows:

Transaction tra_1

tra_1 = CREATE transaction

tra_1.DBMS = “ODBC”

tra_1.database = “myDB”

CONNECT using tra_1

Dw_1. Settransobject (tra_1)

Dw_1. Retrieve ()

While using settrans () the user need not specify an explicit CONNECT or DISCONNECT statement in the script since PB internally calls them whenever required. As part of internal transaction management of DW controls, when the DW needs to access the DB, the DW control issues an internal CONNECT, performs data access and then issues an internal DISCONNECT.

Settransobject () is used when the user goes for a separate transaction object (example SQLCA) or creates a separate one in the script.

The sequences of statements are as follows:

Transaction tra_1

tra_1 = CREATE transaction

tra_1.DBMS = “ODBC”

tra_1.database = “myDB”

CONNECT using tra_1

Dw_1. Settransobject (tra_1)

Dw_1. Retrieve ()

If the user wants to copy DB objects from ONE database to other or copy from one DBMS to another, the data pipeline can be used. The file can be exported from one database and imported to the target database. In the Data Pipeline painter you define a data SOURCE, source database, target database, RETRIEVAL arguments, unions, sorting, SELECTION, and grouping criteria.

If the user wants to copy DB objects from one database to other or copy from one DBMS to another, the data pipeline can be used. The file can be exported from one database and imported to the target database. In the Data Pipeline painter you define a data source, source database, target database, retrieval arguments, unions, sorting, selection, and grouping criteria.

• Regeneration – when you modify an ancestor OBJECT, you can regenerate descendants so they pick up the code changes to the ancestor.
• Optimisation – it is the process of compressing library objects; it removes gaps in libraries and defragments the storage of objects, thus IMPROVING performance. Optimising only affects the layout on disk and not the contents of the objects. Objects are not recompiled. For best performance libraries should be optimised once a week.
• PBD – DW objects are stored in PBLs that are CONVERTED to PBDs THEREBY providing runtime versions of DW objects.

• A DW can be DESIGNED such that the user is prompted to ENTER the parameters for data retrieval while this not possible with data store. If the user calls the RETRIEVE method for a DW control, the DW object EXPECTING an argument, if the user LEAVES it blank, it prompts the user to enter an appropriate value, this behaviour is not supported in data stores.
• The PRINT Set-up dialog box for setting print specifications is not possible in data stores.

It is a non-visual DATA WINDOW. For example if you want to retrieve data from a table without showing it, then you can go for data store. It does not support clicked events but supports delete row (), INSERT row (), retrieve () and update (). It also supports ITEM Error () event.

It is a non-visual data window. For example if you want to retrieve data from a table without showing it, then you can go for data store. It does not support clicked events but supports delete row (), insert row (), retrieve () and update (). It also supports Item Error () event.

ITEM Error () occurs when the data supplied to a particular column in a table fails some validation rules. For example a DW column designed to ACCEPT only integer values throws this error if a string VALUE is passed. DB Error () occurs when INSERT/UPDATE/DELETE/RETRIEVE fails. When it occurs, the DW Control throws up a message box DESCRIBING the error to the DBMS. The user can also get the appropriate error code and THROW up message boxes.

Item Error () occurs when the data supplied to a particular column in a table fails some validation rules. For example a DW column designed to accept only integer values throws this error if a string value is passed. DB Error () occurs when INSERT/UPDATE/DELETE/RETRIEVE fails. When it occurs, the DW Control throws up a message box describing the error to the DBMS. The user can also get the appropriate error code and throw up message boxes.

It is a data window that is MODIFIED or created during runtime. CREATE method can be USED to create or replace the current DW object in the DW control with the newly created DW. Settransobject () needs to be reset with the new DW in the control SINCE the earlier ASSOCIATION would have been DESTROYED.

It is a data window that is modified or created during runtime. CREATE method can be used to create or replace the current DW object in the DW control with the newly created DW. Settransobject () needs to be reset with the new DW in the control since the earlier association would have been destroyed.