Read about corrections and clarifications to released documentation for PowerBuilder 12.5.
CR# | Description |
---|---|
741783 | Use Selected.Mouse object
property in conjunction with Protect object property This note should be added to the Usage section of the DataWindow object property topic Selected.Mouse in the DataWindow Reference: Note: If a column is protected and
dw_control.Object.Selected.Mouse = "No", than you cannot select a
column. You can still select the column header, however, which will
highlight the entire column. You should set Selected.Mouse to "No",
Protect to 1, and Grid.ColumnMove to "No".
Users should also refer to the Protect and Grid.ColumnMove object property topics in the DataWindow Reference. |
736338 | Update to ORCA appendix in Users Guide On the
first page of Appendix B: The OrcaScript Language in the
PowerBuilder Users Guide, it states that the full ORCA tool kit is
available to Sybase partners only, but this is not the case. The
files ship with the product:
|
731412 | Support for 32-bit Outlook and
simple MAPI only At this time only 32-bit Outlook is supported, and the simple messaging application program interface (MAPI). PowerBuilder does not support 64-bit Outlook. |
728727 | Selecting Windows Classic Style
removes the manifest file 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. |
727830 | Overflow of real, double, and
decimal values does not cause runtime errors 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. |
720479 | Corrections to database drivers
and supporting files for SQL Anywhere There
are some corrections to the file names for SQL Anywhere in the Application Techniques topic ODBC Database Drivers and Supporting
Files.
|
718173 | Correction to syntax for
Transparency (DataWindow objects) 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 }" |
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. |
712849 | Find Function Enhancement 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. |
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. |
701504 | Create white list of Web sites for
Web Forms applications 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. |
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 was not updated in
Application Techniques in time for this release. In Application Techniques, everywhere that msvcr71.dll and msvcp71.dll are listed, please add msvcr100.dll and msvcp100.dll to the required DLLs. |
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 will be 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: In 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
Next 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. |