Documentation Updates and Clarifications

This note should be added to the Usage section of the DataWindow object property topic Selected.Mouse in the DataWindow Reference:

Users should also refer to the Protect and Grid.ColumnMove object property topics in the DataWindow Reference.

At this time only 32-bit Outlook is supported, and the simple messaging application program interface (MAPI). PowerBuilder does not support 64-bit Outlook.

Disregard the section in the InfoMaker Users Guide > InfoMaker Environment > Working with InfoMaker > Windows help files on Vista. PowerBuilder and InfoMaker no longer ship with WinHelp.

Corrected Text: When you select the Windows Classic Style check box in the application project, the application appears with the standard controls.

This correction applies to PowerBuilder Users Guide > Running Your Application > Creating Executables and Components > Defining an executable application project.

In the PowerScript Reference topic Arithmetic operators in PowerBuilder, the Errors and overflows section states that "Overflow of real, double, and decimal values causes errors at runtime" but they do not. You can overflow real, double, and decimal values.

This applies to the DataWindow Reference and the InfoMaker Users Guide.

Corrected Text:

PowerBuilder dot notation: dw_control.Object.DataWindow.transparency

Describe and Modify argument: "DataWindow.transparency { = integer }"

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.

The Find function now has a buffer argument. You can use the new buffer argument to find data in the Delete! or Filter! buffers. The default value is Primary! The argument is optional.

long dwcontrol.Find (string expression, long start, long end{, DWbuffer buffer})

This was documented in the 12.1 Release Bulletin, but not added to the core documentation. It should be included in 12.5 and later.

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.

You can set PBAllowDownloadUrls in the Project Painter. It is a white list of Web sites, separated by semicolons. By setting this list, PowerBuilder accepts only the URLs of the sites in this list, which allows you to provide added security to your application. The list is not case-sensitive. Include "http:\\" or "https:\\" in the URLs.

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.

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.

There is a new function in the SoapConnection class. See SetKeepAlive. This affects the Extension Reference.

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.

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.

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.

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.

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

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 will be ignored for the objects that do not support that property.

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.

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