 |
|
Search for in all of Sybase.com |
view all search results  |
|
|
Release Bulletin PowerBuilder® Enterprise 10.5.1
Document ID: DC33822-01-1051-02 Last revised: November 16, 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® Enterprise 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.1 EBF download. ASP Web site targetsPowerBuilder 10.5 is the last version of PowerBuilder Enterprise that will include ASP Web site targets, which enable you to build ASP pages and deploy them to a file system or FTP server. ASP Web site targets will be superseded in version 11 by an alternative technology. JSP targets will continue to be available in PowerBuilder version 11. Software used for SOAP clients for Web servicesPowerBuilder lets you choose between the .NET Web service engine and the EasySoap Web service engine to construct SOAP requests and parse the SOAP messages returned from a Web service. PowerBuilder installs an EasySoap105.dll file that contains the EasySoap++ library in executable form. The EasySoap105.dll file is linked dynamically to the PBSoapClient105.pbx and the PBSoapClient.pbd files. If you want to use the EasySoap Web service engine in a PowerBuilder application, you must import the PBX file to an application PBL or add the PBD to your target. When you deploy your application, you also distribute the contents of the PBX or PBD with its link to the EasySoap++ library. The EasySoap++ library and its use are covered by the GNU Lesser General Public License (LGPL). For a copy of this license, see Gnu--LGPL.txt in the Support.zip file on the PowerBuilder 10.5.1 download page. You may distribute the EasySoap++ library to third parties subject to the terms and conditions of the LGPL. Please read the LGPL prior to any such distribution. The complete machine-readable source code for the EasySoap++ library is provided in the EasySoap.zip file in the Support\WSExtn folder on the CD. In addition, the object code and Microsoft Visual C++ project file for the PBSoapClient105.pbx are provided in the soapclient.zip file in the same directory. These files are provided under the terms of the LGPL so that you can modify the EasySoap++ library and then relink to produce a modified EasySoap105.dll. You can also relink PBSoapClient105.pbx with the modified EasySoap++ import library. According to the terms of the LPGL, it is understood that you will not necessarily be able to recompile PBSoapClient105.pbx to use the definitions you have modified in the EasySoap++ library. Follow the instructions in the Readme.txt file in the soapclient.zip file to build PBSoapClient105.pbx. For information about consuming Web services in PowerBuilder applications, see the chapter on building Web service clients in Application Techniques. 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 PowerBuilder EnterpriseYou can download PowerBuilder Enterprise 10.5.1 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 PowerBuilder Enterprise 10.5.1, you must have already installed version 10.5 of PowerBuilder Enterprise on your computer. To update PowerBuilder:
Installing the PowerBuilder VM on EAServerTo run PowerBuilder components in EAServer, the runtime dynamic shared libraries for the version of PowerBuilder in which the components were developed must be available on the server. The PowerBuilder runtime files on the client and the server must be at the same build level. To find out which version of the PowerBuilder virtual machine (VM) is installed with EAServer, see the “Product Compatibilities” section of the release bulletin for EAServer. If the PowerBuilder 10.5.1 VM is not installed, run the PBVM setup program to update the PowerBuilder runtime files. To update the PowerBuilder VM:
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] Pipeline execution with JDBC driver failsExecuting a pipeline with the destination Adaptive Server Enterprise 12.5 when using the JDBC driver fails with the database error 2762. [CR 338371] Table updates not handled by OLE DB provider for Adaptive ServerThe PB DataDirect OLE DB data provider for Adaptive Server Enterprise does not correctly handle table updates in the Database painter. [CR 338363, CR 338366] DataDirect ODBC XML driver issuesYou cannot create an ODBC XML data source name (DSN) using the DataDirect 5.1 ODBC driver. [CR 408671] Informix interface does not work with UTF-8The IN9 Informix database interface cannot update and retrieve data when the Informix server uses the UTF-8 character set. The interface works correctly with ANSI and DBCS. [CR 349535] Alter table limitations with OLE DB and Microsoft SQL ServerWhen you connect using OLE DB and change the name or width of a column in a Microsoft SQL Server 2000 database using Alter Table in the Database painter, the column is moved to the end of the table and all its data is lost. To prevent this from occurring, PowerBuilder does not allow you to alter a table's column name and column size. You can alter the table outside the painter using ISQL scripts or at runtime using PowerScript® functions. Note that SQL scripts to alter a column's name are available only on the SQL Server 2000 client. [CR 348581] PB 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 PB 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 if you connect using ODBC, OLE DB, JDBC, or ADO.NET. The stored procedure runs correctly using the Oracle native driver. [CR 343297] OraOleDB faster than Oracle8ADOProviderWhen you use an OLE DB connection to an Oracle9i database, the Table list or View list displays much more quickly in the Database painter if you use OraOleDB instead of the Oracle8ADOProvider. [CR 341835] Connection issues with CnnPoolIn the Database painter, attempting to connect to an Oracle9i or Oracle 10g database from an Oracle9i client fails after a connect and disconnect if the CnnPool database parameter is set to ‘Yes’. This is because the Oracle9i client does not support connection pooling with a Unicode environment handle. [CR 355639] 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] Microsecond portion of Adaptive Server times not retrievedWhen you use the OLE DB interface to connect to an Adaptive Server Enterprise database and select a column with the DateTime or Time datatype, the microsecond portion of the time value is not retrieved. When you use the ODBC and JDBC interfaces, the microsecond portion of a DateTime column value is retrieved correctly, but the microsecond portion of a Time column value is not. [CR 399257] 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 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 Dynamic SQL format 4 provides only one function, GetDynamicNumber, for all numeric datatypes. This function does not work correctly 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 available in PowerBuilder 11. [CR 403862] EAServer issuesEAServer release bulletin For additional issues, please refer to the release bulletin for the version of EAServer that you are using on the Sybase Product Manuals Web site. Byte datatype support for PowerBuilder components in EAServerTo fully support the byte datatype in PowerBuilder components
hosted in EAServer, you must apply EBF 13293 to EAServer 5.3 and
add a file named pb.types to the EAServer repository.
This file must contain the following line: Deploying an NVO Web service or accessing a Web serviceDue to an upgrade in the underlying Axis technology, you must apply EBF 13293 to EAServer 5.3 before you deploy a PowerBuilder NVO as a Web service or access a Web service from a JSP target running in EAServer. Additionally, to make the JSP Web service feature work, you
must assign the following value to the -Dorg.apache.axis.transport.http11.chucked=false [CR 415834, CR 398194] Byte[ ] datatype issue with Web services hosted in EAServerAlthough EAServer can successfully return a byte[ ] datatype, it does not correctly handle the byte[ ] datatype as an input parameter. Any Web method that calls a Web method hosted in EAServer with a byte[ ] argument as an input parameter fails at runtime. This affects only Web methods hosted in EAServer. Web methods with a byte[ ] argument that are hosted in other servers can be successfully invoked from a JSP that is hosted in EAServer. [CR 306821] SSL connection to EAServer 5.x failsEAServer versions 5.2 and 5.3 use Transport Layer Security (TLS) to establish secure connections between a client and server. TLS is a protocol based on the Secure Sockets Layer (SSL) that can authenticate both the client and the server and create an encrypted connection between them. PowerBuilder clients that rely on the previous version of the EAServer SSL client runtime and use mutual authentication cannot establish an SSL connection using the default settings. To disable support for TLS and use the previous version of the SSL client runtime, set the environment variable JAGSSL to true in the serverstart.bat file before you start EAServer. You can also set this environment variable in an EAServer client installation: set JAGSSL=true [CR 402979] Calling a .NET Web service with EAServer causes runtime errorWhen EAServer 5.3 is used as a JSP server, calling a .NET Web service method that uses a byte array for a parameter in a JSP page causes a runtime error. [CR 378724] Consuming a .NET Web service from a PowerBuilder NVOIf you call a .NET Web service from a PowerBuilder component running in EAServer, you must deploy the Sybase.PowerBuilder.WebService.Runtime.dll, Sybase.PowerBuilder.WebService.RuntimeRemoteLoader.dll and the dynamically generated .NET assembly to the EAServer bin directory (EAServer 5.x) or the EAServer JDK/bin (EAServer 6.0) directory. [CR 446351] Creating an EJB client application for an EJB deployed to EAServer 6.0Building EJB client applications for EJBs running in EAServer 6.0 requires you to take some additional steps when you create the EJB client proxy and when you create the client. See the New Features section of the PowerBuilder 10.5.1 Online Help for more information. EJB client issuesCreateJavaVM does not produce debug informationDue to limitations in the Sun JDK 1.4, setting the isdebug argument of the CreateJavaVM method of the EJB client JavaVM class to true does not produce a vm.out debug information file when you use JDK 1.4. To work around this problem, use JDK 1.3 when you need debug information. You can change the JDK used in the development environment from the Java page of the System Options dialog box. [CR 296630] Installation issuesUninstall removes EAServer profiles from registryUninstalling PowerBuilder removes the EAServer profiles from the HKEY_CURRENT_USER\Software\Sybase\PowerBuilder\N.N\JaguarServerProfiles key in the registry, where N.N represents the version of PowerBuilder you are removing. If you need to uninstall and reinstall PowerBuilder, export this registry key to a file before you uninstall PowerBuilder. [CR 347732] JSP issuesJSP Web DataWindow DTC pages display incorrectly in Enterprise PortalJSP Web DataWindow DTC pages that use the XHTML or XML Generation Format options do not display correctly when deployed to Enterprise Portal. [CR 357759, CR 357760] See “EAServer issues” for additional issues. Column link problems with non-English charactersIn a Web DataWindow DTC, if a column link property is set on a string column that contains Unicode data (non-English characters) and the value of this column is passed as a parameter to a target page, the target page does not display the Unicode data in the parameter value correctly. The data is displayed as garbage characters. This is caused by a defect in Internet Explorer. [CR 359511] Web DataWindow custom component cannot be found in JSP Web DataWindow wizardWhen you deploy a Web DataWindow custom component to EAServer 6.0 and create a JSP Web DataWindow page using the wizard, the Web DataWindow custom component cannot be found. The following workaround might solve the issue:
Now you can select the Web DataWindow custom component. [CR 445109] 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] PowerDesigner plug-in issuesOLE controls are not supportedCode for OLE controls is not generated when you reverse-engineer a PowerBuilder target to an OOM. [CR 359805] Case sensitivity in external function namesWhen you reverse-engineer and then regenerate a PowerBuilder application, an external function with a case-sensitive name such as GetCurrentDirectoryA fails. The workaround is to specify an alias for the function, for example: public function ulong GetCurrentDirectoryA (ulong textlen, ref string dirtext) library “KERNEL32.dll” alias for "GetCurrentDirectoryA;ansi" [CR 358442] 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, 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] Text does not wrap correctly in rich text controlWhen WordWrap is enabled, text should wrap automatically to the next line when it reaches the right margin of the rich text control. But, in PowerBuilder 10.5.1, although WordWrap is enabled in a rich text control, the text is not wrapped correctly. This occurs because PowerBuilder sets 8 ½" x 11" as the default page size for the control. To work around this issue, change the page size to match the control size. The text will wrap correctly. [CR 441593] 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] Web services issuesSee “EAServer issues” for additional Web service issues. Using a trace tool with .NET Web servicesAlthough you can still use the built-in SOAP logging option with EasySoap Web services, PowerBuilder does not provide the same option with .NET Web services. Instead, you can use a third-party tool to trace .NET proxy calls for debugging purposes. There are two kinds of trace tools you can use:
[CR 419815] Structures with array membersCalling a PowerBuilder custom class user object Web service that passes or returns a structure of arrays can fail. [CR 407611] SOAP header cannot be modified in an EasySoap Web serviceUser authentication security in an EasySoap Web service cannot be implemented because this security must be included in the <soap:Header> section, which cannot be modified in PowerBuilder. [CR 351464] Web services client raises exception with machine codeIf a Web services client application is built as a machine-code executable, and a Web service proxy function has an array of longlong and double datatypes as an argument, calling this function raises an exception. A Pcode executable works correctly. [CR 360444] Array members with null valuesIf a Web service returns an array with a null value, you can declare an Any datatype variable to hold it; however, if you use an array variable to hold the null return value, PowerBuilder reports a runtime error. If the null value is returned for an embedded array, PowerBuilder throws an exception whether you use an Any variable or an array variable to hold the return value. When you use a Web service that returns an array or an embedded array, you should test whether that value is null using the IsNull method before deciding how to proceed. [CR 415207] If you attempt to debug and run a workspace that imports a structure with an array member that returns a null value, then attempt to assign the null value to another variable, this can cause PowerBuilder to throw an exception. [CR 409850] EasySOAP Web services do not support some built-in datatypesPowerBuilder EasySOAP Web services do not support the anyType and ur-type XML Schema built-in datatypes. [CR 341513] Web services across time zonesWhen an application consumes a Web service that uses the date, time, or datetime datatypes, it is possible that the service implementation processes and returns different data for application users who access the service from different time zones. This is typically the result of design considerations of the Web service and not the result of precision differences or translation errors between the Web service and the application that calls it. [CR 429611] 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] PBNI objects not found at runtimeA call to the PBDOM_OBJECT GetContent function works correctly in the development environment but fails at runtime with the error, “Error calling method of a PBNI object.” This occurs because the object cannot be found. The workaround is to reference all PBDOM and PBNI objects in PowerScript code so that they are included in the executable file. [CR 343299] Translation Toolkit cannot translate PBLs from previous versionIf you want to translate PBLs from a version of PowerBuilder prior to PowerBuilder 10, you must first migrate them to PowerBuilder 10 or later. See the online Help for the Translation Toolkit for more information. [CR 349513] 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] Web ActiveX download fails on Windows XPThe DataWindow Web Control for ActiveX fails to download its CAB file to a client browser running on Windows XP if the Microsoft Active Template Library (ATL) module, atl71.dll, is not present in the Windows\System32 directory. The CAB file downloads successfully if the ATL DLL is present. Product compatibilitiesEAServerPowerBuilder 10.5.1 has been tested with EAServer 5.3 GA (Build 53016) patched with EBF 13293 and EAServer 6.0 GA (Build 60093) patched with EBF 14142. If you want to establish an SSL conection between Power Builder 10.5.1 and EAServer 6.0, you must copy the files available in the \lib folder of EBF 14142 to a corresponding folder in the EAServer client. To run PowerBuilder components in EAServer, the runtime dynamic shared libraries for the version of PowerBuilder in which the components were developed must be available on the server. The PowerBuilder runtime files on the client and the server must be at the same build level. Using different build levels on client and server machines might result in unpredictable behavior or data corruption. SQL 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). Note:If you want to upgrade to SQL Anywhere 10.0 after installing PowerBuilder 10.5.1 with Adaptive Server Anywhere 9.x, you must run the ASA9DBto10 tool after upgrading. ASA9DBto10 is available in the Support folder. Refer to the instructions in the Readme.txt file in the Support\ASA9DBto10 folder. PowerDesignerPowerBuilder 10.5.1 has been tested with PowerDesigner 12.1. Enterprise PortalPowerBuilder 10.5.1 has been tested with Enterprise Portal 6.0 with EAServer 5.3. JavaPowerBuilder 10.5.1 is compatible with JDK 1.5.x. Apache TomcatPowerBuilder 10.5.1 JSP targets have been tested with Apache Tomcat 4.1.30. To use Web DataWindows and access EAServer components in JSP pages that you will deploy to a Tomcat server, you must add the following JAR files to the %Tomcat%\shared\lib directory:
You should also add the JAR files required by your DBMS, such as jconn2.jar for jConnect. Application ServersEJB client functionality has been tested with EAServer 5.3, WebLogic 8.1, Oracle 9i AS, Oracle Application Server 10g, and WebSphere 5.0. GhostscriptThe DataWindow Save as PDF feature has been tested with AFPL Ghostscript version 8.53. Documentation updates and clarificationsAuthentication methods for SOAPConnection classThe methods for the SOAPConnection class are not included in the printed and online versions of the PowerBuilder Extension Reference or are documented incorrectly. For more information about these methods, refer to the Help file installed with PowerBuilder or the PowerBuilder 10.5 Release Bulletin on the Sybase Product Manuals Web site. PBNI Application WizardThe following information is not included in the printed and online versions of the PowerBuilder Native Interface User’s Guide and Reference. It is included in the Help file installed with PowerBuilder. If Visual Studio .NET 2005 is installed on your computer, a PBNI Application wizard is installed in the ..\Microsoft Visual Studio 8\VC\VCProjects and ..\Microsoft Visual Studio 8\VC\VCWizards directories when you install PowerBuilder. You use the wizard in the same way as the wizards for earlier versions of Visual Studio. InsertPicture 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. New RecheckRows database parameterThe RecheckRows database parameter is not described in the Connection Reference. In Microsoft SQL server, if a table has an insert, update, or delete trigger, the number of affected rows returned to the SQLNRows property of the Transaction object after an INSERT, UPDATE, or DELETE command depends on the driver. With an ADO.NET driver, the value returned is the sum of the rows affected by the command itself and the trigger. When you are connected to Microsoft SQL Server using ADO.NET or OLE DB, you can set the RecheckRows runtime database parameter to 1 to recheck how many rows of data were affected by the INSERT, UPDATE, or DELETE command itself and return that value in the SQLNRows property. Setting RecheckRows to 1 before issuing an INSERT, UPDATE, or DELETE command causes a SELECT @@ROWCOUNT command to be executed. To improve performance, you should set it only when required, and reset it to the default value of 0 after use. Example 1To set RecheckRows to 1, type the following in code: SQLCA.DBParm="RecheckRows=1" BindSPInput database parameter applies to Oracle 10gThe O10 driver for Oracle 10g is not listed as supported in the description of the BindSPInput database parameter in the Connection Reference. BindSPInput applies to the O10 interface. 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.
Rich text deployment issueChapter 41, “Deploying Applications and Components,” in Application Techniques lists the files that must be deployed with an application that uses rich text, but omits the following requirements. When the application is run remotely on a server, the ActiveX control (tp4ole11.ocx) must be registered on the client computer. In PowerBuilder 10.5 EBF 5048 and later builds, the ActiveX control does not need to be registered on the client if the required files are in the same directory as the PowerBuilder runtime files or in an RTC subdirectory of that directory. Microsoft update affects DataWindow Web ActiveXIf the Cumulative Security Update for Internet Explorer (912812) or a subsequent update is installed on the computer where the DataWindow Web Control for ActiveX (Web ActiveX) is running, a browser refresh does not refresh the control correctly. This update is described in Microsoft Security Bulletin MS06-013, published in April 2006. To work around this issue, move the <OBJECT> tag from the main HTML file to a separate JavaScript file, as shown in this example: // HTML file <HTML> <HEAD> <TITLE>test</TITLE> </HEAD> <BODY bgColor="white" PSPARAMS=""> <P>Put your data here </P> <P> </P> <P> <div id="DivID"> <script src="createElement.js"></script> </div> </BODY> </HTML> The createElement.js JavaScript file contains the Object tag:
// createElement.js file
var d = document.getElementById("DivID");
d.innerHTML =
'<OBJECT id="OBJECT1" style="WIDTH: 627px; HEIGHT: 320px" codeBase="psdwc105.cab" classid="CLSID:A5A51503-A5A5-1000-8000-080009AC61A9">'
+'<PARAM NAME="_Version" VALUE="65536"></PARAM>'
+'<PARAM NAME="_ExtentX" VALUE="16589"></PARAM>'
+'<PARAM NAME="_ExtentY" VALUE="8467"></PARAM>'
+'<PARAM NAME="_StockProps" VALUE="2"></PARAM>'
+'<PARAM NAME="Caption" VALUE=""></PARAM>'
+'<PARAM NAME="SourceFileName" VALUE="test.psr"></PARAM>'
+'<PARAM NAME="DataWindowObject" VALUE="test.psr"></PARAM>'
+'<PARAM NAME="LogId" VALUE=""></PARAM>'
+'<PARAM NAME="LogPass" VALUE=""></PARAM>'
+'<PARAM NAME="dbParm" VALUE=""></PARAM>'
+'<PARAM NAME="SuppressEvents" VALUE="0"></PARAM>'
+'<PARAM NAME="VScrollBar" VALUE="0"></PARAM>'
+'<PARAM NAME="HScrollBar" VALUE="0"></PARAM>'
+'<PARAM NAME="HSplitScroll" VALUE="0"></PARAM>'
+'<PARAM NAME="LiveScroll" VALUE="0"></PARAM>'
+'</OBJECT>';
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.
|
|||||||||||||||||||||||||||||||||||||||||||
