powerbuilder 5.0

Release Notes for PowerBuilder[TM] Enterprise Version 5.0 PowerBuilder[TM] Professional Version 5.0 PowerBuilder[TM] Desktop Version 5.0 � 1991-1996 Sybase, Inc. and its subsidiaries. All rights reserved. Updated 5/21/96 If you previously installed a Beta build of PowerBuilder 5.0, please read the BETA USER NOTES section of this document. If you have used a prior version of PowerBuilder, please read the PREVIOUS VERSION USER NOTES section of this document. *********************************************************************** General Information ----------------------- To Begin: To install PowerBuilder 5.0, please run SETUP.EXE from this CD and select the version of the software you wish to install on your workstation. NOTE: Do not run setup16.exe or setup32.exe; these are two subroutines called by setup.exe. Some things to be aware of during the setup process: - If you press the escape key once setup has begun to install files, you will be notified of your intent to cancel as soon as the current file has finished copying. - In Windows 95, you must physically connect to the drive from where you will be installing PowerBuilder. Network Neighborhood will not recognize it otherwise, and you will get an error. Installing off a Network drive ------------------------------ 32-bit only: If you have installed PowerBuilder on a network, you need to make some local Registry entries in order to run. To make these entries, locate the Setup on the CD. Run the setup as normal. When the products screen appears, modify the paths to the network drive and directories where the following components of Powersoft products *WERE* installed: 1) Path to Network PB shared - This is the path to the Powersoft DLLs (or Shared Files). WinNT default: pwrs\sys32 Win95 default: Program Files\Common Files\Powersoft Shared 2) Path to Network PB - This is the path to PB050.EXE. WinNT default: pwrs\pb5i32 Win95 default: Program Files\Powersoft\PowerBuilder 5.0 3) Path to Network SQLAnywhere - This is the path to the SQLAnywhere files. If SQLAnywhere was not installed on the network, uncheck this component. The default on both WinNT and Win95 is sqlany50\win32. 4) Path to PB Demo Database - This is the path to the Demo Database used by the Examples). WinNT default: pwrs\pb5i32\ex\code Win95 default: Program Files\Powersoft\PowerBuilder 5.0\ Examples\Code Continue with the install normally. When the install finishes, you will have a program item for PowerBuilder, SQLAnywhere ISQL, the Demo Database and Uninstall on the local machine. Latest Sybase SQLAnywhere release --------------------------------- This CD contains release 5.2 of Sybase SQLAnywhere. Running PowerBuilder Applications --------------------------------- When you build PowerBuilder applications (executables) on Windows 95, you will need to register them in the Windows Registry and set up an APP PATH for them, so that the executable can find the Powersoft DLLs and any database files that it needs. We suggest using the AppPath Utility in the Application Gallery to do so. Running 16-bit Applications on a 32-bit machine ----------------------------------------------- If you create a 16-bit compiled code executable on a 32-bit machine, make sure you have the 16-bit PowerBuilder DLLs available on that machine, or the executable will not run correctly. 16 vs 32-bit External Function Calls ------------------------------------ If you are migrating an application to 32-bit, be aware that any DLLs to which you make external function calls also must be available in 32-bit versions. 64K script limit for 16-bit Compiled Executables ------------------------------------------------ When creating 16-bit compiled code executables, please be aware that very large scripts may raise a problem with the 64K segment limit on the 16-bit platform. The behavior you will see when this happens is a compiler error indicating that segment is too large. To discover what routine is causing the problem, look in the .log file to discover the line and the .c file. Bring the .c file into an editor and go to the line, which will probably be in the middle of a generated function. Go to the beginning of the function and the name of the routine will be in a comment. Looking further up in the file, you can find the name of the class in a comment. To correct this error, partition your scripts into smaller sections, using object or global functions. PowerWeb -------- All installs are adding an icon called PowerWeb. This is a small HTML file which lets you link to the Powersoft Web site. If you do not have a web browser installed on your system, this entry will display a blank icon. Editing SQL in a DataWindow, Pipeline or Query Object ------------------------------------------------------ If you are in graphical mode and choose to edit the SQL, hitting the SQL icon on the toolbar will get you there. When you are in SQL edit mode, the SQL icon becomes depressed and cross-hatched and indicating that it is toggled to SQL mode. Hit the SQL icon again to return to graphical mode. LongString columns in DataWindows --------------------------------- Existing DataWindows that have LongString columns (i.e. SQLServer text) in their result set will include the column in the WHERE criteria if the existing table has its update characteristics set to key and updatable columns or key and modified columns (and you modify the text field). In the case of SQLServer this results in the error described below. If you set the DBParm staticbind=0 then DataWindows dynamically describes the result set and flags the LongString column so it does not appear in the WHERE clause. If you export your data window and add the "updatewhereclause=no" clause to your DataWindow definition and import the object, it will work with staticbind=0! A sample column definition is: table(column=(type=long update=yes updatewhereclause=yes key=yes name=c_integer dbname="pbqa.c_integer" ) column=(type=char(32766) update=yes updatewhereclause=no name=c_text dbname="pbqa.c_text" ) New DataWindows now generate the appropriate syntax. The Database painter also works correctly when staticbind=0 is set. New WSOCK32.DLL for Distributed PB - POWERBUILDER ENTERPRISE ONLY ---------------------------------- The currently distributed version of WSOCK32.DLL from Microsoft causes a memory leak in Distributed PowerBuilder Server applications using the WinSock driver in Windows 95. This is a known Microsoft problem, fixed in QFE 4.00.951 version of WSOCK32.DLL. We have obtained permission from Microsoft to distribute a file called WSOCKUPD.EXE with PowerBuilder 5.0. This file is a self-extracting file containing the WSOCK32.DLL v.4.00.951 update. PowerBuilder developers may also distribute this DLL to their end-users. You can find a copy of this file on the CD in the \support directory. Please copy this DLL if you are building Distributed PowerBuilder applications that use WinSock. When you run the file, it will update WSOCK32.DLL in your Windows 95 SYSTEM directory, replacing any file it finds there. Calling MAPI ------------ Use of the 16-bit mail API (MAPI) is not supported under 32-bit PowerBuilder - you need to use the 32-bit version. Library for Lotus Notes - POWERBUILDER ENTERPRISE ONLY ----------------------- There are now 32-bit versions available to access either 16 or 32-bit Notes Clients. PowerBuilder 5.0 is compatible with Lotus Notes Version 4.0. Silent Install -------------- The PowerBuilder install allows you to create a setup file that can be used to run multiple identical installs. To see how to use this feature, see the "PowerBuilder Installa