Using Tab controls in scripts – PB Docs 90
Using Tab controls in scripts This section provides examples of tabs in scripts: Referring to tab pages in scripts Referring to controls on tab pages Opening, closing, and hiding tab pages Keeping track of tab pages Creating tab pages only when needed Events for the parts of the Tab control Referring to tab pages in…
Using the Code Examples application – PB Docs 90
Using the Code Examples application You run the Code Examples application from the development environment. To run the Code Examples application: Select File>New from the menu bar, select Workspace from the Workspace tab, and click OK. Navigate to the PowerBuilder 9.0Code ExamplesExample App folder, type a name for the workspace, and click Save. Select Add…
Using window arrays – PB Docs 90
Using window arrays To create an array of windows, declare an array of the datatype of the window. For example, the following statement declares an array named myarray, which contains five instances of the window w_employee:
|
1 |
w_employee myarray[5] |
You can also create unbounded arrays of windows if the number of windows to be opened is not…
Handling row errors – PB Docs 90
Handling row errors When a pipeline executes, it may be unable to write particular rows to the destination table. For instance, this could happen with a row that has the same primary key as a row already in the destination table. Using the pipeline-error DataWindow To help you handle such error rows, the pipeline places…
Handling PBDOM exceptions – PB Docs 90
Handling PBDOM exceptions PBDOM defines an exception class, PBDOM_EXCEPTION, derived from the standard PowerBuilder Exception class. The standard Text property of the Exception class can be used to obtain more detail on the nature of the exception being thrown. The class extends the PowerBuilder Exception class with one method, GetExceptionCode, that returns the unique code…
About preferences and default settings – PB Docs 90
About preferences and default settings Many PowerBuilder applications store user preferences and default settings across sessions. For example, many applications keep track of settings that control the appearance and behavior of the application, or store default parameters for connecting to the database. PowerBuilder applications can manage this kind of information in initialization files or in…
Chapter 35 Printing from an Application – PB Docs 90
Chapter 35 Printing from an Application About this chapter This chapter describes how to use predefined functions to create printed lists and reports. Contents Topic Printing functions Printing basics Printing a job Using tabs Stopping a print job Advanced printing techniques Document get from Powerbuilder help Thank you for watching.
Accessing a database from a COM component – PB Docs 90
Accessing a database from a COM component To take advantage of MTS or COM+ support for transaction management, you need to use one of the database interfaces supported by MTS or COM+ to connect to your database. For more information about database connections for components developed in PowerBuilder, see Connecting to Your Database . COM…
Printing data – PB Docs 90
Printing data You can use a DataStore to print data on a remote server if the server is running on Windows or Solaris. Platform note The following example would not work on HP-UX or AIX. On these platforms, EAServer uses a windows-free version of the PowerBuilder runtime environment that does not provide support for graphical…
Connecting to a COM server – PB Docs 90
Connecting to a COM server To access a method associated with a component in the COM server, the PowerBuilder client connects to the component using its programmatic identifier (ProgID) or its class identifier (CLSID). You can use a tool such as OLEVIEW or the OLE tab in the PowerBuilder Browser to view the Program ID…