Show TOC

Documentation Updates and ClarificationsLocate this document in the navigation structure

Read about corrections and clarifications to released documentation for PowerBuilder 12.6.

Table 1: PowerBuilder Documentation Issues
CR# Description
N/A SAP JVM replaces JDK

PowerBuilder no longer uses the Sun Java Development Kit (JDK) with a Java Runtime Environment (JRE). It uses the SAP JVM instead. Disregard mention of the JDK in the online help.

763052, 709871 Use platform argument in OrcaScript command Build Executable to specify whether to build 32- or 64-bit native application.
The OrcaScript command is now:
build executable <exeName> <iconName> <pbrName> <pbdflags> [machinecode] [newvstylecontrols] [platform]

The platform argument is used to specify whether to build a 32- or 64-bit native application. Specify x64 to build a 64-bit application, otherwise it builds a 32-bit application.

Applies to: Users Guide > Appendix B: The OrcaScript Language > OrcaScript Commands.

760309 New option for OrcaScript command scc refresh target

In addition to full, migrate, and incremental, there is a new option: 3pass. This option performs a full rebuild of the application. You should use it instead of full when there are complex inherited relationships.

Applies to: Users Guide > Appendix B: The OrcaScript Language > OrcaScript Commands.

758835 Errors during painter compilation and application build
PowerBuilder can report these issues:
  • While compiling a painter, PowerBuilder reports errors if the object is not found in the most recently used database and it fails to connect to that database.
  • While building, PowerBuilder reports errors only if it fails to connect to the most recently used database. PowerBuilder appears to run the embedded SQL, but it does not report errors even if the object is not found in the most recently used database.
  • PowerBuilder ignores errors except the connection error during the build.

Applies to: Disabling database connection when compiling and building in the PowerScript Reference and the PowerBuilder Users Guide.

755443 LibraryDirectory changes CR-LFs and tabs in comments to spaces.

When you obtain a list of objects in a PowerBuilder library using LibraryDirectory, you receive a tab-separated list with one object and its information per line. If the comments for an object includes carriage returns, line feeds, or tabs, those are all converted to spaces.

Applies to PowerScript Reference > PowerScript Functions > Library Directory.

753920 Code for using ShowPopupHelp with CHM files
To display the context help for a control, the string needs to include a reference to the text file that was included in the CHM to define the context help with ::/ between the name of the CHM file and the name of the text file. For example:
ShowPopupHelp("my_app.chm::/myapp-popups.txt", this, 100)
In PowerBuilder Getting Started, Code some Help events and preview the window, the code to call the popup help in the login window is:
(ShowPopupHelp("pbtutor.chm::/popups.txt", this, 100)) //sle_userid
(ShowPopupHelp("pbtutor.chm::/popups.txt", this, 200)) //sle_password
In the same document, Modify the frame menu, the code to call the help (steps 3 and 5) should read:
ShowHelp ("pbtutor.chm", Index!)
ShowHelp ("pbtutor.chm", Keyword!, "")
753679 SAP branding

All company branding mentioned in the documentation is updated to SAP in PowerBuilder and InfoMaker.

Go to https://websmp103.sap-ag.de/supportInformation published on SAP site for technical support.

Go to http://help.sap.com/powerbuilder for current information on PowerBuilder documentation and http://help.sap.com/infomaker for InfoMaker.

If you install SQL Anywhere, SQL Central is the new name for Sybase Central.

730975 References to WinHelp in the InfoMaker Users Guide are outdated

The InfoMaker Users Guide section on Using online Help mentions WinHelp (imhlp###.hlp). All online help is in the HTML help file (imman###.chm). WinHelp no longer ships with InfoMaker, so references to it should be disregarded.

720138, 621820 New SoapConnection functions

As of PowerBuilder 12.5.x, there are two functions in the SoapConnection class. See EnablePreAuthentication and SetKeepAlive. This affects the Extension Reference.

None SoapConnection methods

Corrected Text: In the Extension Reference, these methods are for .NET Web services engines only: AddToBypassList, DynamicCast, RemoveBypassList, SetBypassProxyOnLocal, SetClientCertificateFile, SetUseDefaultProxySetting, and UseIntegratedWindowsAuthentication. These methods are for EasySoap Web services engines only: SetSoapLogFile and UseConnectionCache.

715058 GetFileOpenName function behavior differences between operating systems

The initdir parameter in GetFileOpenName function uses some different algorithms in Windows 2000/XP/Vista from Windows 7, which are described in detail in Initdir Parameter Behavior in GetFileOpenName Function.

705028 Providing support for NULL values in EAServer Components

Corrected text: Proxy objects do not include the suffix "_N" in the function name. In Application Techniques, Defining the component interface, the paragraph that begins "If you allow null values in the prototype for a component method, PowerBuilder appends a ā€œ_Nā€ suffix to the method name" should be removed entirely.

699475 In Connecting to Your Database > Chapter 9: Using Microsoft SQL Server > SQL Server 2008 features > Support for new datatypes in SQL Server 2008, the first sentence of the Precisions Settings paragraph should read: "PowerBuilder includes a column labeled "Dec" in the Columns view of the Database painter..."
692447 Incorrect datatype mappings for PowerBuilder .NET

Corrected text: PowerBuilder Date and Time variables need to be converted to DateTime when calling a C# assembly. You can call PowerBuilder assemblies with the Date and Time variables and perform the conversion within the assemblies. See PowerBuilder .NET Datatype Mapping.

677259 Windows Forms and Web Forms require two DLLs, in addition to DLLs currently listed: msvcr100.dll and msvcp100.dll. The documentation was updated in the PowerBuilder .NET Features Guide and Deploying Applications to .NET; however, it has not been updated in Application Techniques.

In Application Techniques, everywhere that msvcr71.dll and msvcp71.dll are listed, add msvcr100.dll and msvcp100.dll to the required DLLs.

668659 Debugger Changes

New text: Only a debug version can be debugged; the release version cannot be debugged. If a debug version does not exist, the debugger fails. This is not related to the build type set in the Project painter.

639448 Unsupported Properties, Events, and Functions

New text: You cannot use the Border property for custom controls. If multiple objects are selected including the custom control, you can set the Border property for the objects that do support the Border property. The setting is ignored for the objects that do not support that property.

638096 Oracle8i native interface is not available in PB 11.5 and later

Corrected text: Table 1-4 in Checklist for deployment in Deploying Applications and Components to .NET includes pbo84125.dll but support for the Oracle8i native interface has been discontinued as of PowerBuilder 11.5. The pbo84125.dll should be removed from the table.

635140 Unsupported Properties, Events, and Functions

Updated text: As of PowerBuilder 12.1, the DisplayOnly property for RichTextEdit is supported.

624234 Application Server Plug-in

Corrected text: Application Techniques and the Users Guide include information about the Application Server plug-in, but support for this plug-in has been discontinued as of PowerBuilder 12.0.

624126 ToolbarAlignment window property

New text: The Features Guide does not list Floating! as an unsupported enumerated value for the ToolbarAlignment property. In migrated applications that retain this value, toolbars align at the top of a window.

605201 Behavior Changes for DataWindow Objects

New text: PrintPage behavior: In PowerBuilder Classic, when the return code is set to 1, the page is not printed. In PowerBuilder .NET, when the return code is set to 1, the page prints.