 |
|
Search for in all of Sybase.com |
view all search results  |
|
|
Release Bulletin PowerBuilder® Desktop/Professional 10.5.1
Document ID: DC33823-01-1051-01 Last revised: December 4 , 2006 Accessing current release bulletin informationA more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the product release, use the Sybase Product Manuals Web site. Accessing release bulletins at the Sybase Product Manuals Web site
Product summaryEnclosed is Sybase PowerBuilder® Desktop or Professional version 10.5.1, which is compatible with the following platform and operating system configurations:
DataDirect database driversThe PB DataDirect ODBC drivers and OLE DB data providers from DataDirect Technologies are delivered with this release under a limited contract. They will be removed from the final PowerBuilder 10.5.x EBF download. Special installation instructionsThis section describes special installation instructions for PowerBuilder. Before you installBefore you install this release, shut down any applications running on your system. Restart your system after all the installations are complete. The executable files in this release extract setup files to the folder specified by your TMP environment variable, or the folder specified by your TEMP environment variable if TMP is not defined or specifies a directory that does not exist. Make sure you have enough disk space on the drive containing this folder before beginning the installation. To specify an alternative location, open the System Properties dialog box from the Windows Control Panel, select the TMP user variable (or TEMP if TMP does not exist) on the Environment or Advanced tab page, and specify a location that has sufficient space. Installing PowerBuilderYou can download PowerBuilder 10.5.1 Desktop and Professional editions from the PowerBuilder page of the Sybase EBFs/Maintenance site. Download the files you require and extract the contents of the zip files following the instructions in the download notes that accompany the release. To install either of these products, you must have already installed version 10.5 of that product on your computer. To update PowerBuilder Desktop or Professional:
Changed functionality in this versionFor a description of changes in the PowerBuilder 10.5.1 release, see the New Features section of the PowerBuilder online Help file. To view the Help file, select Help>Welcome to PowerBuilder 10.5 from the PowerBuilder menu. See “Migration information” for more information. Known problemsDatabase connectivity issuesWindow is a reserved word in ASAIn Adaptive Server® Anywhere 9, the word “window” is a reserved word. As a result, SELECT statements on a column with the name window do not work correctly. There are several ways to work around this issue:
[CR 334166] DataDirect ODBC XML driver issuesYou cannot create an ODBC XML data source name (DSN) using the DataDirect 5.1 ODBC driver. [CR 408671] DataDirect Oracle driver issuesIf you create a table in the Database painter using the PB DataDirect 5.1 Oracle driver and give it a name that has all lowercase characters, the table columns are not visible in the Layout view. They display correctly after you select Tables>Refresh. [CR 348038] The DataDirect OLE DB data provider for Oracle does not correctly handle inserts, updates, and display for Simplified Chinese and Traditional Chinese data. [CR 338372] Oracle stored procedures with output parametersAn Oracle stored procedure with output parameters produces an ORA-01036 error at runtime. [CR 343297] RPC calls with non-Unicode Adaptive Server databasePowerBuilder can access Unicode data in Unichar and Univarchar columns in Adaptive Server® Enterprise databases that do not use a Unicode character set. You must set the UTF8 database parameter to 1 and configure the server to support both Adaptive Server direct conversions and Unicode conversions. To configure the server, the database administrator must run the following command: sp_configure, "enable Unicode conversion", 1 Declare procedure calls work correctly with this configuration, but RPC calls that use these columns are not currently supported. [CR 378850] ASE version 15 with ODBC driverRetrieving and updating data in a DataStore with a TimeStamp datatype fails when you connect to an ASE version 15 server using the Sybase ASE ODBC driver. This is due to a bug in the ASE ODBC driver. [CR 416248] Stored procedure call returns incorrect value with SQL Anywhere 10With an ODBC connection to SQL Anywhere® 10, a stored procedure call with a numeric INOUT parameter that contains a value with zero digits in the last two or more places, such as 100, 1000, or 1200, returns an incorrect value. This is due to a bug in the SQL Anywhere 10.0 ODBC driver. [CR 443233] DataWindow issuesSave As PDF fails on Windows 2003 ServerSaving as PDF using the Distill method fails at runtime on Windows 2003 Server. This problem is caused by a Group Policy that by default disallows installation of printers that use kernel-mode drivers. Kernel-mode drivers have access to system-wide memory, and poorly written drivers can cause system failures. To allow installation of kernel-mode drivers, follow these steps:
[CR 349868] AutoSize Height issues with header bandWhen two reports are included one above the other in the header band of a DataWindow® object and the AutoSize.Height property is set to true for the header band and false for the detail band, the DataWindow displays incorrectly in preview. The lower report overlaps the upper report. The report displays correctly if the Autosize.Height property is set to true in both the header and detail bands.[CR 405033] XSL-FOP save as PDF does not support graphic controlsUse the distill method to export the data in DataWindow objects that contain graphic controls, such as ovals and rectangles, to PDF. The XSL-FOP method does not work correctly for graphic controls. [CR 303829] Limitations in default PostScript driversThe PostScript drivers installed with PowerBuilder do not support searching the generated PDF file. [CR 332365] The PostScript drivers installed with PowerBuilder do not support searching the generated PDF file, and when a DataWindow object has more columns than fit on a single page, so that data is wrapped to a new page in the PDF file, sometimes the last column on each page is clipped. The workaround is to use an alternative driver. See the PowerBuilder 10.5 Installation Guide on the Sybase Product Manuals Web site for how to install and use an alternative driver. [CR 324579, CR 332365] Print preview mode disabled with ShowPrintDialogWhen a DataWindow is in print preview mode, calling the Print method with the ShowPrintDialog argument set to true causes the DataWindow to display in normal mode. [CR 401182] Print preview mode limitationsYou can set the paper size and print margins from the Print Specifications tab page of the Properties dialog box for a rich text control. The settings you make modify the display of the control in both the standard and preview modes. However, you cannot open the Properties dialog box in preview mode. You must make paper size and print margin settings before you set the control display to preview mode. [CR 435746] AutoSize group header band distorted in print preview modeThe AutoSize group header band is formatted correctly in normal mode but it is distorted in print preview mode. The column headers at the bottom of the group header band are overlapped by the detail band. [CR 421766] TreeView DataWindow collapses when deleting or inserting a rowIf a row is inserted or deleted when the TreeView DataWindow is in an expanded state, the TreeView DataWindow collapses. No workaround is known for this issue. This issue will be fixed in the next PowerBuilder 10.5.1 EBF release. [CR 439781] SaveAs to Excel8! in script enables the encoding optionWhen you select Excel8! as the file type in the Save As dialog, the Encoding drop-down list is enabled and selected. This option is irrelevant for the Excel format and should always be disabled. If you change the file type from Excel to any other option, the encoding field is disabled. [CR 444616] Decimal and longlong datatype support issuesCompiler error when maximum value assignedAssigning the maximum value to a decimal variant without a decimal portion causes a compiler error. [CR 380713] Precision lost in message boxPrecision is lost when you display a decimal variant with more than 16 bits in a message box. [CR 390258] Dynamic SQL Format 4 does not work with longlong datatypePowerBuilder 10.5.1 supports the longlong datatype and increases the range of the decimal datatype, but DSQL format 4 provides only one function, GetDynamicNumber, for all numeric datatypes. This function does not work properly for data having the longlong datatype, or with high-range data of the decimal datatype. A new function for longlong and decimal datatype data will be implemented in a future release. [CR 403862] Menu and toolbar issuesStock file image size inconsistentIn contemporary menus and toolbars, stock files and external files with multiple images are loaded differently. For stock files, PowerBuilder loads 32x32 images first. For external files, PowerBuilder loads 16x16 images first. PowerBuilder stock files include two types of files: BMP and ICO. Most BMP files have 16x16 images, and most ICO files have both 16x16 and 32x32 images. When you use a stock file, the BMP file is loaded with the 16x16 image but the ICO file is loaded with the 32x32 image. As a result, the size of the stock image used is inconsistent. [CR 421716] RightToLeft property not supportedThe RightToLeft property is not supported in menus and toolbars in this release. [CR 395702] Display issues with some driversWith some display card drivers, if you highlight a menu item with the mouse, a white block displays under the mouse point and is moved when you move the mouse. This is a limitation of the display card drivers and cannot be fixed in PowerBuilder. There are two techniques that might solve the issue:
[CR 414452] Rich text control issuesScroll issues when input fields bound to DataStoreAt runtime, if you insert input fields in a RichTextEdit control and bind the data source to a DataStore, then call ScrollNextRow or ScrollNextPage, the cursor disappears and you cannot scroll the DataWindow as expected. [CR 419757] Rich text application deployment issuesWhen you deploy a rich text application to a server or client machine, you must also copy the rich text DLL and OCX files in the Sybase\Shared\PowerBuilder\RTC directory to the PowerBuilder VM directory on the deployment computer or to a directory in the application’s path. For more information on the list of files that must be deployed with an application that uses rich text, see the chapter on deploying applications and components in Application Techniques. You can use the PowerBuilder Runtime Packager to deploy the required rich text files with your application. You do not need to register the rich text OCX file if it is copied or deployed to the directory containing the PowerBuilder VM. For more information on the runtime packager, see the chapter on deploying applications and components in Application Techniques. [CR 426800] Inserting a document in a rich text control failsYou cannot insert a document into a rich text control when the control’s DisplayOnly property is set to true. If you try to do this, PowerBuilder displays a runtime error message. [CR 435744] UTF-8 encoding in rich text controlIf you insert an HTML file with UTF-8 encoding in a rich text control, the file does not display correctly unless the character set is indicated. In a future release, the encoding will be determined from the byte order mark of the HTML file, and it will not be necessary to indicate the character set. [CR 415495] SCC issuesAdding an object to SCC whose name contains non-English characters failsWhen you put a workspace that supports multiple languages under source control and attempt to add all files to SCC, PowerBuilder crashes if one or more of the object names contain non-English characters. [CR 342590] Other issuesPowerTips using the XP styleSome window controls, such as Pictures, PictureButtons, and PictureHyperLinks, can display PowerTip text. When the cursor is on the control, the tip text displays but disappears after several seconds. Moving the cursor from the control to another control with PowerTip text and back again causes the tip to display again, but moving the cursor from the control to the window background or a control without PowerTip text and back does not. This problem is caused by a Microsoft issue with Comctrl32 Version 6. [CR 403814] UpdateBlob SQL statement supports only UTF-16LEThe UpdateBlob SQL statement updates garbage characters to the database if the encoding of the blob variant is not UTF-16LE. For Adaptive Server Enterprise, PowerBuilder crashes if the encoding of the blob is ANSI or UTF-8 and it contains fewer than 10 characters. [CR 353231] Truncated string in saved EMF fileIf a string in a text control in a DataWindow object is longer than can be displayed in the control in the Design view in the DataWindow painter, an EMF file saved in the painter or at runtime displays with the string truncated. [CR 342797] Throws clause removed from menu events when menu item is movedIf you add a user-defined event to a menu item and specify in the Prototype window that the event throws an exception, and then move the menu item to another location, the Throws box in the Prototype window is cleared. [CR 290236] String formatting function not Unicode enabledThe String function used to format a string does not have an encoding argument to allow you to specify the encoding of the resulting string. As a result, the string returned can contain garbage characters. To work around this issue, convert the string to a blob and then back to a string using the encoding parameters provided in the Blob and String conversion functions: ls_temp = String(long, "address" ) // format string lb_blob = blob(ls_temp, EncodingUTF16LE!) ls_result = string(lb_blob, EncodingANSI!) // convert // to string [CR 361568] Product compatibilitiesSQL AnywhereIn version 10.0, Adaptive Server Anywhere and SQL Anywhere Studio have been renamed SQL Anywhere. The suite is now referred to as SQL Anywhere. The database server is referred to as SQL Anywhere server. PowerBuilder 10.5.1 has been tested with Adaptive Server Anywhere (ASA) 9.0.2 (Build 3044), ASA 9.0.2 Runtime Edition (Build 3044), and SQL Anywhere 10.0 (Build 2464). GhostscriptThe DataWindow Save as PDF feature has been tested with AFPL Ghostscript version 8.53. Documentation updates and clarificationsInsertPicture enhancement for RichTextEditThe InsertPicture function for the RichTextEdit control now supports WMF, JPEG, PNG, GIF, and TIFF files in addition to bitmap files. The list of modified functions in the New Features book and the description of InsertPicture in the PowerScript® Reference do not include this enhancement. List of DataDirect ODBC files incorrectThe list of PowerBuilder DataDirect ODBC database drivers and files in Chapter 41, “Deploying Applications and Components,” in Application Techniques is incorrect. The following table lists the required files for each supported interface.
Migration informationYou can migrate a PowerBuilder application from any version of PowerBuilder directly to any later version. Before you migrate to a later version, read the following Technical Document to learn about changes in PowerBuilder that might affect your application: Migrating PowerBuilder Applications. Back up your files and use the Migration Assistant to identify obsolete code before you migrate. OLE DB performance with Microsoft SQL ServerIn PowerBuilder 10.5.1, when you use the OLE DB database interface with a Microsoft SQL Server database and retrieve data into a DataWindow or use an embedded SQL cursor in a SELECT statement, server-side cursors are used to support multiple command execution. If this has a negative impact on performance, try increasing the size of the Block database parameter to 500 or more, or adding the following line to the [Microsoft SQL Server] section in the PBODB105.ini file to turn off server-side cursors: ServerCursor = 'NO' Toolbar changes in PowerBuilder 10.5In the Menu painter, you can now add a toolbar to a standalone main window as well as to an MDI frame. PowerBuilder adjusts the size of the main window to accommodate the toolbar. If your application currently uses a visual user object as a toolbar in a main window, the adjustments that PowerBuilder makes might affect the display of your toolbar and conflict with adjustments that your scripts make to display microhelp. You can replace your toolbar user object with a toolbar designed in the Menu painter or continue to use your existing toolbar. To ensure that your existing toolbar displays correctly, set the window’s ToolbarVisible property to false in a script or on the Toolbar page in the Properties view. To avoid conflicts, you should also move any microhelp position adjustment code into an event that runs after the Open event of the window. Icon changes in PowerBuilder 10.5In PowerBuilder 10.5, many of the icons used in the PowerBuilder and InfoMaker user interfaces were changed. When you migrate an application to PowerBuilder 10.5 or later, any stock icons used in the application are updated automatically. For users who prefer to use the existing icons, a zip file that contains 24 icon files and more than 500 bitmap files used in previous versions of the products is available on the CodeXchange Web site. Change in Date function behaviorWhen you use the Date function with a string
argument, PowerBuilder attempts to match the input string to a date
format in the regional settings on the computer. In PowerBuilder
10 and later, if a complete match is not found, PowerBuilder attempts
a partial match. For example, if you use Technical supportEach Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area. Other sources of informationUse the Sybase Getting Started CD, the SyBooks CD, and the Sybase Product Manuals Web site to learn more about your product:
Sybase certifications on the WebTechnical documentation at the Sybase Web site is updated frequently. Finding the latest information on product certifications
Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.
Sybase EBFs and software maintenanceFinding the latest information on EBFs and software maintenance
Accessibility featuresThis document is available in an HTML version that is specialized for accessibility. You can navigate the HTML with an adaptive technology such as a screen reader, or view it with a screen enlarger. PowerBuilder 10.5.1 and the HTML documentation have been tested for compliance with U.S. government Section 508 Accessibility requirements. Documents that comply with Section 508 generally also meet non-U.S. accessibility guidelines, such as the World Wide Web Consortium (W3C) guidelines for Web sites. Note:You might need to configure your accessibility tool for optimal use. Some screen readers pronounce text based on its case; for example, they pronounce ALL UPPERCASE TEXT as initials, and MixedCase Text as words. You might find it helpful to configure your tool to announce syntax conventions. Consult the documentation for your tool. For information about how Sybase supports accessibility, see Sybase Accessibility. The Sybase Accessibility site includes links to information on Section 508 and W3C standards. For more information about accessibility features of PowerBuilder, see the chapter on building accessible applications in Application Techniques. For a Section 508 compliance statement for PowerBuilder, go to the Voluntary Product Assessment Templates page.
|
|||||||||||||||||||||||||||||||||||||||||||
