Using the Preview tab to connect in a PowerBuilder application – PB Docs 2017
Using the Preview tab to connect in a PowerBuilder application The Preview tab page in the Database Profile Setup dialog box makes it easy to generate accurate PowerScript connection syntax in the development environment for use in your PowerBuilder application script. As you complete the Database Profile Setup dialog box, the correct PowerScript connection syntax…
Referencing parts of a graph – PB Docs 2017
Referencing parts of a graph You use dot notation to reference these display properties. For example, one of the properties of a graph’s title is whether the text is italicized or not. That information is stored in the boolean Italic property in the TitleDispAttr property of the graph. For example, to italicize title of graph…
Using the JDBC Interface – PB Docs 2017
Using the JDBC Interface Contents About the JDBC interface Preparing to use the JDBC interface Defining the JDBC interface About this chapter This chapter describes the JDBC interface and explains how to prepare to use this interface and how to define the JDBC database profile. For more information For more detailed information about JDBC, go…
What to do next – PB Docs 2017
What to do next For instructions on preparing to use and then defining an ODBC data source, see Using the ODBC Interface. For instructions on preparing to use and then defining a JDBC database interface, see Using the JDBC Interface. For instructions on preparing to use and then defining an OLE DB data provider, see…
Troubleshooting Your Connection – PB Docs 2017
Troubleshooting Your Connection Contents Overview of troubleshooting tools Using the Database Trace tool Using the SQL statement trace utility Using the ODBC Driver Manager Trace tool Using the JDBC Driver Manager Trace tool About this chapter This chapter describes how to troubleshoot your database connection in PowerBuilder by using the following tools: Database Trace SQL Statement…
Using database profiles – PB Docs 2017
Using database profiles What is a database profile? A database profile is a named set of parameters stored in the registry that defines a connection to a particular database in the PowerBuilder development environment. Why use database profiles? Creating and using database profiles is the easiest way to manage your database connections in PowerBuilder because you can:…
Reading AutoCommit and Lock values from an external text file – PB Docs 2017
Reading AutoCommit and Lock values from an external text file As an alternative to setting the AutoCommit and Lock properties in a PowerBuilder application script, you can use the PowerScript ProfileString function to read the AutoCommit and Lock values from a specified section of an external text file, such as an application-specific initialization file. To read AutoCommit…
How you can use the Database Trace tool – PB Docs 2017
How you can use the Database Trace tool You can use information from the Database Trace tool to understand what PowerBuilder is doing internally when you work with your database. Examining the information in the log file can help you: Understand how PowerBuilder interacts with your database Identify and resolve problems with your database connection Provide useful…
Copying AutoCommit and Lock syntax from the Preview tab – PB Docs 2017
Copying AutoCommit and Lock syntax from the Preview tab The easiest way to specify AutoCommit and Lock in a PowerBuilder application script is to copy the PowerScript syntax from the Preview tab in the Database Profile Setup dialog box into your script, modifying the default Transaction object name (SQLCA) if necessary. As you complete the Database…
Coding PowerScript to set values for AutoCommit and Lock – PB Docs 2017
Coding PowerScript to set values for AutoCommit and Lock Another way to specify the AutoCommit and Lock properties in a script is by coding PowerScript to assign values to the AutoCommit and Lock properties of the Transaction object. PowerBuilder uses a special nongraphic object called a Transaction object to communicate with the database. The default Transaction object…