Java support – PB Docs 120
Java support You must deploy the PowerBuilder pbjvm120.dll file with any applications or components that use the Java Runtime Environment (JRE), and there must be a JRE installed on the target computer. The JRE is required for EJB clients, JDBC connections, and saving as PDF using XSL-FO. You can copy the JRE installed with PowerBuilder…
Building a style from scratch – PB Docs 120
Building a style from scratch Once you understand how form styles work, you can build one from scratch. To build a form style from scratch: Create a new window. Place a DataWindow control in the window. In the Properties view for the control, name the control using one of the special names. For the list…
Completing the style – PB Docs 120
Completing the style To complete your form style, enhance the window and menu to provide the processing you want. For example, you can: Work with the central DataWindow control Add controls to the window Define actions (functions that appear as actions in your form style) Modify the menu and its associated toolbar Write scripts for…
Deployment Techniques – PB Docs 120
Deployment Techniques This part explains how to package your application for deployment and what files you need to deploy. Document get from Powerbuilder help Thank you for watching.
Chapter 35 Packaging an Application for Deployment – PB Docs 120
Chapter 35 Packaging an Application for Deployment About this chapter This chapter tells you how to prepare a completed executable application for deployment to users. Contents Topic About deploying applications Creating an executable version of your application Delivering your application to end users Document get from Powerbuilder help Thank you for watching.
Garbage collection and memory management – PB Docs 120
Garbage collection and memory management The PowerBuilder garbage collection mechanism checks memory automatically for unreferenced and orphaned objects and removes any it finds, thus taking care of most memory leaks. You can use garbage collection to destroy objects instead of explicitly destroying them using the DESTROY statement. This lets you avoid runtime errors that occur…
Exception handling in PowerBuilder – PB Docs 120
Exception handling in PowerBuilder When a runtime error occurs in a PowerBuilder application, unless that error is trapped, a single application event (SystemError) fires to handle the error no matter where in the application the error happened. Although some errors can be handled in the system error event, catching the error closer to its source…
Rich text and the end user – PB Docs 120
Rich text and the end user All the editing tools described throughout this chapter and in the chapter on working with rich text in the PowerBuilder Users Guide can be made available to your users. What users can do Users can: Use the toolbars for text formatting Use the pop-up menu, which includes using the…
Programmable OLE Objects – PB Docs 120
Programmable OLE Objects You do not need to place an OLE control on a window to manipulate an OLE object in a script. If the object does not need to be visible in your PowerBuilder application, you can create an OLE object independent of a control, connect to the server application, and call functions and…
Performing some final housekeeping – PB Docs 120
Performing some final housekeeping When your application has finished processing pipelines, you need to make sure it takes care of a few cleanup chores. These chores basically involve releasing the resources you obtained at the beginning to support pipeline execution. Garbage collection You should avoid using the DESTROY statement to clean up resources unless you…