PasteLowercase PB.INI option
When you paste PowerScript statements such as FOR...NEXT and CHOOSE CASE into a script, the statements are pasted in lowercase. To paste statements in uppercase, add the following line to the [PB] section of the PB.INI file:
Exporting and importing XML with CDATA sections
You can export the name of a column in a CDATA section using the syntax <![CDATA[columnname]]>. You can export the value of a column using the syntax <![CDATA[~t columnname]]>. The ~t is used to introduce a DataWindow expression, in the same way that it is used in the Modify method. You can also use an expression such as ~t columnname*columnname to export a computed value to the XML.
You can import a value into a column using the syntax <![CDATA[ columnname]]>. Note that this syntax in a template has different results for import and export: it imports the column value but exports the column name.
You cannot import an XML file that has a ~t expression in a CDATA section.
Changes in the Release database parameter
The PowerBuilder native driver for Adaptive Server® Enterprise now uses the Release database parameter exclusively to determine the capabilities of the Open Client software being used to communicate with Adaptive Server. You must set the Release database parameter to the version of your Open Client software, not to the version of Adaptive Server to which you connect. The SYC driver automatically determines the version of each Adaptive Server you connect to after a successful connection has been established. Knowing the capabilities of both the client and server allows the SYC driver to customize PowerBuilder's integration for each Adaptive Server database connection.
For more information, see the online Help for Release.
OJSyntax parameter now available for SYC
The OJSyntax database parameter is now available for Adaptive Server. You can set the parameter by selecting a value from the Outer Join Syntax drop-down list on the Syntax page of the Database Profile Setup dialog box. For more information, see the online help for OJSyntax.
Configuring Java VM initialization
When you connect to a source control system, PowerBuilder creates a Java VM by default. For certain SCC programs, such as Borland’s StarTeam or Serena’s TrackerLink, the Java VM created by PowerBuilder conflicts with the Java VM initialized by the SCC program. To prevent Java VM conflicts, you must add the following section and parameter setting to the PB.INI file:
By adding this section and parameter setting to the PB.INI file, you prevent PowerBuilder from creating a Java VM when it connects to a source control system.
If you include this parameter setting in your PB.INI file and your source control system requires a Java VM, the source control system typically initializes the Java VM used by PowerBuilder on connection of the workspace to source control. The Java VM must have PowerBuilder in its classpath; otherwise you will not be able to deploy JSP targets from this workspace. PowerBuilder must exit to unload a Java VM. To successfully deploy JSP targets, you must first disconnect the current workspace from source control, then close and reopen PowerBuilder without reconnecting to source control. You can reconnect the workspace to source control after you deploy JSP targets.