前往Shuct.Net首页

Shudepb PB反编译专家长时间以来,为业内同类软件事实上的唯一选择.细节,彰显专业.态度,决定品质.

关于PowerBuilder的搜索

PowerBuilder EBFs PowerBuilder 9.0.1 EBF (Emergency Bug Fix)The files included in this EBF are 32-bit from PowerBuilder 9.0.1 EBF Build 7096 (Post 9.0.1 MR). Dear Sybase Customer,Please note that you are being provided with an EBF release of the Sybase software you requested. In addition to the fixes from the previous scheduled release of the product (GA, Interim or EBF release), this EBF release contains a fix designed to address your particular reported problem.Please note that this release has undergone minimal testing; it has not been subjected to the Sybase QA team's customary standard suite of tests. It is a requirement that you upgrade to the next official PowerBuilder release on http://downloads.sybase.com as soon as it is available. In addition to securing fixes to other problems included in the official release, you will then have a release that has undergone more intensive QA testing.In the interim, please backup your installation, as you normally would do prior to making any updates to your install. Likewise, Sybase recommends testing your application(s) with the patch prior to using it in production.Sincerely,Sybase Support Important NotesThis 9.0.1 EBF build has received QA automation and manual testing. It is being provided on an Emergency basis. If you decide to use this EBF it will be necessary for you to retest your entire application.By applying this EBF, you also agree to apply the next official release on the Sybase downloads site: Either a PowerBuilder release for EAServer (which can also be used by customers who do not use EAServer), a Maintenance Release, or the "final" EBF when a PowerBuilder version has reached it's official End of Life date, whichever comes first.NOTE: If you wish to receive automated e-mails when new PowerBuilder releases are posted to the Sybase downloads site, make sure you have set up a MySybase account and the preferences have been set up so that, at a minimum, "Software Downloads" is included for your "MyNews" profile, "EBFs/Updates" is included for your "Downloads" and "Support" profiles, and "PowerBuilder" is included for your "Products" profile. Changed Functionality in this EBFHeap manager included in pbvm90.dll:You do not need to distribute the libjsybheap.dll file with PowerBuilder 9.0.1 applications. The functionality provided in libjsybheap.dll in PowerBuilder 9.0 has been moved into pbvm90.dll, and libjsybheap.dll is no longer installed or required. Any copy of libjsybheap.dll already installed on your system will not be removed when you install this PowerBuilder 9.0.1 EBF. It will not be referenced and can safely remain on your system or be removed.Format of WMF files saved from DataWindows changed:In PowerBuilder 9.0, the format of WMF files created by saving a DataWindow object was changed to fix a crash issue. However, the fix removed the header information that allows the WMF file to be viewed in other applications. The format has now been changed again to restore the header information in PB 9.0 EBF builds 6096 and greater and the 9.0.1 maintenance release. [CR 292406]EasySoap++:PowerBuilder Enterprise includes the EasySoap++ library in executable form in EasySoap.dll, which is dynamically linked to PBsoapclient90.dll. 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 folder on your PowerBuilder 9 CD or on the Web at http://www.gnu.org/copyleft/lesser.html. The complete machine-readable source code for the EasySoap++ library and the object code and Microsoft Visual C++ project file for the PBSoapClient90.dll were provided under the terms of the LGPL with PowerBuilder Enterprise 9.0 and 9.0.1. These files have been modified for this EBF release to enable the use of both rpc and document binding styles when calling Web services on WebSphere from SOAP clients (CR 330798). The updated files are provided with this EBF in the Easysoap.zip and SoapClient.zip files.After applying this EBF, you should regenerate all SOAP Web service proxies generated in PowerBuilder 9.0 or 9.0.1 that use the document type to ensure that they work correctly with the PBSoapClient90.dll provided with this EBF.For more information about using these files and distributing the EasySoap++ library, see Section 2.1.2 in the PowerBuilder Enterprise 9.0.1 release bulletin at http://download.sybase.com/pdfdocs/pbr0901e/pbentrb.pdf.Context-sensitive menu items for PBD files:In the System Tree and Library painter, the pop-up menu for a PBD has only two menu items, Remove Library and Show. There is no pop-up menu for objects in a PBD. In previous releases, you could display the context-sensitive menus associated with a PBL and its objects by changing the extension of a PBD file from .pbd to .pbl. For PBDs created in this release, PowerBuilder recognizes that the renamed file is a PBD file and displays the appropriate pop-up menu for the PBD itself and no pop-up menu for the objects it contains. You cannot copy or move objects into or out of PBDs renamed as PBLs. You can still view properties, events, and functions in the System Tree, and drag event and function prototypes from a renamed PBD in the System Tree to a Script view. [CR 323919] Known IssuesLocation of Ghostscript files for save as PDF:When you save a DataWindow object as PDF using the distill method, PowerBuilder searches in the following locations for an installation of GNU Ghostscript:1. The Windows System registry.2. The relative path of the pbdwe90.dll file (typically Sybase\Shared\PowerBuilder).3. The system PATH environment variable.If GNU Ghostscript is installed using either gs705w32.exe (for Ghostscript 7.05) or gs706w32.exe (for Ghostscript 7.06), the path is added to the Windows registry, therefore the gs7.0x\bin directory does not need to be added to the system PATH environment variable as instructed in the installation guide.userconfig.xml file for save as PDF using XSL-FO:On DBCS platforms, you must modify the userconfig.xml file in the Shared\PowerBuilder\fop-0.20.4\conf directory to give the full pathname of the files you use to support DBCS fonts. For more information, see the chapter on exporting and importing XML data in the User's Guide. Fixed Issues to be HighlightedOut of Memory Message:Previous PB 9.0.1 EBFs included a regression that resulted in an "out of memory" message when trying to create an executable for a "large" application. The problem also occurred if a "full rebuild" was initiated from the workspace. This issue was fixed on November 21st, and is included in this EBF and EBFs created after that date (which can be determined by looking at the datestamp on the PB EBF DLLs). [CR 339856]SCC Fixes:If you open and close instances of the Library painter during an SCC session, performing actions such as add to or remove from source control in different instances of the Library painter could cause PowerBuilder to crash. In addition, changing the length of the version information string could corrupt the data. For example, changing the version number from 9 to 10 adds an extra character to the string, and the version number appeared to revert to 1. These issues were fixed on November 17th and are included in this EBF and EBFs created after that date (which can be determined by looking at the datestamp on the PB EBF DLLs). [CR 338457]PB Desktop - ASA Database:PowerBuilder Desktop was hardcoded to accept only certain ODBC drivers. Support for ASA 9 needed to be included for both PB 8 and PB 9 Desktop versions. This issue was fixed on October 3, 2003, and is included in this EBF and EBFs created after that date (which can be determined by looking at the datestamp on the PB EBF DLLs). [CR 334215] RequirementsPB:The minimum requirement for applying this EBF is the PB 9.0.1 Maintenance Release (Build 6533), which is also available on the Sybase downloads site.EAServer:If you do not use EAServer and you are using an earlier build of PowerBuilder 9.0.1, you can install this EBF to update your PowerBuilder 9.0.1 installation.If you do use EAServer, the minimum requirement for using this PowerBuilder EBF is EAServer 4.2.2 (Build 42211). This requirement applies whether EAServer is installed locally or on a remote deployment server. Failure to upgrade EAServer to the appropriate version may result in corruption of data.This EBF Release includes a file called libjcc.dll. The version of this file included in this distribution is intended for use with PowerBuilder only. You should continue to use the libjcc.dll installed in your %EAServer%\dll directory with EAServer. Do not replace %EAServer%\dll\libjcc.dll with the file in this distribution.Running PB Components in EAServer: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 may result in unpredictable behavior or data corruption. EBF Installation1) Create a temporary folder and extract the contents of the EBF zip file into the folder.2) Copy the following folders to a new location to provide a backup:\SYBASE\PowerBuilder 9.0\SYBASE\Shared\PowerBuilder\SYBASE\Shared\DataDirect\SYBASE\Shared\Web Targets (for Enterprise edition users only)\SYBASE\Infomaker 9.0 (for InfoMaker users only)3) Shut down any applications running on your system.4) Run the Setup.exe file in the temporary directory created in step 1 above.5) After the installation is complete, delete the temporary folder created in step 1 above.6) Reboot your system.7) Perform a full rebuild of your PowerBuilder application in the Library painter, to ensure that all descendant objects are synchronized with their ancestors and to incorporate any compiler fixes in your code.These DLLs are considered an interim patch. However, they are deployable and supported.Question: What is meant by "supported"? Answer: If you encounter a regression (i.e. something that worked previously and is now broken) as a result of using this EBF build, please report the problem and include the EBF build number that you are using.Thank you,Sybase Support