The Message object – PB Docs 70
The Message object The Message object is a predefined PowerBuilder global object (like the default Transaction object SQLCA and the Error object) that is used in scripts to process Microsoft Windows events that are not PowerBuilder-defined events. When a Microsoft Windows event occurs that is not a PowerBuilder-defined event, PowerBuilder populates the Message object with…
More about user objects and the registry – PB Docs 70
More about user objects and the registry The registry stores information a program needs to access a registered object. The information is stored in the registration database. To update the registry, the Registry Editor reads registry update files (.REG) and inserts the information in the database. What are all the identifiers for? GUIDs and CLSIDs…
Using a RichTextEdit control – PB Docs 70
Using a RichTextEdit control A RichTextEdit control in a window or user object lets the user view or edit formatted text. Functions allow you to manipulate the contents of the control by inserting text, getting the selected text, managing input fields, and setting properties of all or some of the contents. You define RichTextEdit controls…
Populating TreeViews – PB Docs 70
Populating TreeViews You must write a script to add items to a TreeView. You can’t add items in the painter as with other list controls. Although you could populate all the levels of the TreeView at once, TreeView events allow you to populate only branches the user looks at, which saves unnecessary processing. Typically, you…
About deploying applications on Windows – PB Docs 70
About deploying applications on Windows After you have built your application and created its executable and dynamic library files, you need to set up your users’ machines to run the application. Chapter 35, “Packaging an Application for Deployment”, has a checklist of the application and environmental components that you need to provide to your users….
Developing and deploying in a multiplatform environment – PB Docs 70
Developing and deploying in a multiplatform environment PowerBuilder makes it easy to share files and do part of the development work on one platform and part on another. This section discusses file-sharing considerations, both during development and for a deployed application. Moving and sharing files across platforms You can move PowerBuilder files and resources to…
Setting up each end user – PB Docs 70
Setting up each end user Once you’ve added the deployment and application files to the target computer, you must perform some additional tasks to properly set up each end user who needs to run PowerBuilder applications: Edit shell startup files Copy the .WindU file Configure printers Editing shell startup files This task involves editing each…
Planning the look of your application – PB Docs 70
Planning the look of your application Each platform PowerBuilder runs on has an identifiable look that marks its native applications as belonging to that system. To a large extent, PowerBuilder adjusts the appearance of controls, menus, and windows so that they look right on each platform. However, you do have to be careful how you…
Managing client connections – PB Docs 70
Managing client connections To allow the server to handle client connections successfully, you need to write some logic to specify how and when the server will begin listening for connections. In addition, you need to add logic to handle client requests for services. Version 5 clients cannot connect to Version 6 or 7 servers Because…
Recording errors in a log file – PB Docs 70
Recording errors in a log file To record errors generated by COM objects running in MTS to the Windows NT system application log, create an instance of the ErrorLogging service context object and invoke its log method. For example:
|
1 |
ErrorLogging erlinfo_base |
|
1 |
this.GetContextService("ErrorLogging", & |
|
1 |
erlinfo_base) |
|
1 |
erlinfo_base.log("Write this string to log") |
Document get from Powerbuilder help Thank you for watching.