Release Notes for PowerBuilder[TM] Version 6.5 (Wintel)

(c) 1991-1998 Sybase, Inc. and its subsidiaries. All rights reserved.
Updated 7/20/98

************************************************************************
If you are viewing this file in Wordpad, please use the word-wrap option
************************************************************************

Thank you for choosing PowerBuilder as your development tool!  Please read this document to learn about last minute updates to the product and documentation.
 
************************************************************************
BEFORE INSTALLING:
MAKE SURE THAT THE SQLANYWHERE DATABASE IS NOT RUNNING
************************************************************************

Section I:    General Information
Section II:   PowerBuilder Documentation Addendum

===============================
Section I: General Information
===============================

System Requirements
-------------------

Windows
- 486 PC or higher
- 16 MB RAM (24 recommended)
- 45 MB hard drive space, depending on configuration
- CD ROM drive
- VGA monitor
- Windows 95 or Windows NT 3.51 or higher for development
- Windows 95, Windows NT, or Window 3.x  for deployment

Support Statements (this information also appears in the PowerStudio readme)
------------------
* 16-bit Applications not supported on 32-bit platform

Since the PowerBuilder development environment can produce applications for 16 or 32-bit native deployment on Microsoft Windows, the applications must be deployed to the corresponding Windows platform. 16-bit applications are only supported on Microsoft Windows 3.x

* Termination or elimination of 16-bit deployment capabilities

Sybase is committed to supplying application development tools for strategic enterprise platforms. In order to provide our customers with the highest quality products and the most up to date functionality, we will continue to focus our efforts on the mainstream market. PowerBuilder 6.x is the last release to support 16-bit deployment on Windows 3.1. Starting with the next major release the development environment will only produce 32-bit executables (p-code or machine) for Microsoft Windows.

* Limited Win-OS2 support

PowerBuilder is built and tested on several standard operating systems, Microsoft Windows, Sun Solaris, HP-UX, and IBM AIX. While our development and testing process focuses on these operating systems as the primary development and deployment platforms, Sybase will make best attempts to resolve or work around any compatibility problems encountered while running PowerBuilder applications with IBM Win-OS2 provided the issue is reproducible under Microsoft Windows as well. As with any bug, it must be reproduced and documented so that it can be assigned a case number.

* Limited Exceed PC X-Server support

PowerBuilder is built and tested on several standard operating systems, Microsoft Windows, Sun Solaris, HP-UX, and IBM AIX. While our development and testing process focuses on these operating systems as the primary development and deployment platforms, Sybase will make best attempts to resolve or work around any compatibility problems specific to PowerBuilder applications encountered while running an Exceed v6.0 PC X-Server, provided it does not adversely affect cross-platform consistency or capabilities, including all Enterprise development and deployment aspects of PowerBuilder. Other PC X-Servers would be addressed only if the issue is reproducible on the platform's primary graphics head. As with any bug, it must be reproduced and documented so that it can be assigned a case number.

* Save and close all applications before uninstalling ADT

Uninstalling the Advanced Developer Toolkit (ADT) without first uninstalling PowerBuilder will cause Windows NT to crash.  Please be sure to save and close all applications before performing an uninstall procedure.  Alternatively, if you uninstall PowerBuilder first (before uninstalling the ADT), Windows NT will not crash.

* Preferred Image Editor not configured for InfoMaker

After InfoMaker is installed the icon in the InfoMaker Toolbar for the preferred picture editor does not function correctly.  To correct this problem, edit the pictview.ini file to include the following statement in the Editor section.  
	[Editor]
	program=C:\Program Files\Sybase\ArtGal\wimgedit.exe

* No default pbl file for InfoMaker during Custom installation

If you do not install the InfoMaker tutorial during a Custom installation, there is no default .pbl file for InfoMaker.  During the initial launch, Infomaker will prompt you with a default .pbl file name.   You should select "No" to the default, and then enter any suitable name for the .pbl file.  If you click "Yes", the program will close, and you will be prompted again when you launch InfoMaker the next time. 

* Profile feature sample out of date

The sample file (profiler.pbp) offered with the profile feature is out of date, and will thus give an error message.  Any source file created by the user will work correctly and can be used instead of the sample file.

(end of information in PowerStudio readme)

Generators
----------
The PowerBuilder COM Object Generator and the PowerBuilder JavaBean Proxy Generator are included on this CD, but must be installed separately. The JavaBean Proxy Generator requires the ObjectSpace JGL 3.1.0 library and JDK 1.1.6 

Connecting to DB2
-----------------
We now include an Intersolv driver for connecting to DB2.  This is available on all platforms.  Detailed information is available in Online Help.

Database Information
--------------------
SQLAnywhere 5.5.04 is installed for Windows 32-bit platforms.

Note when installing SQL Anywhere and Object Cycle, two entries are made in the ODBC manager:
  Sybase SQL Anywhere 5.0  5.05.041867  WOD50T.DLL
  Sybase SQL Anywhere 5.5  5.05.041867  WOD50T.DLL
They are exactly the same, except for the name. As a result, two entries will appear in the ODBC administrator. Although they both work correctly, third party products which install databases (like Riverton HOW) will register the data source name with the more recent version.

Oracle 8 Driver - PowerBuilder 6.0 has an option to install the Oracle 8 native database interface.  For further information, see online help.  

DirectConnect
-------------
PBDIR60.DLL will not connect due to problems identified after the final PowerBuilder 6.5 build.  The fixes for the DirectConnect driver will be posted on http://support.sybase.com.  To install the fix, rename the file installed by PowerBuilder 6.5, download the file PBDIR60.DLL, and replace the file installed by PowerBuilder 6.5.

The PowerBuilder DirectConnect interface will ONLY support connections to a DB2/MVS database via the DirectConnect for MVS access service Version 11.1.1 P4 or higher. At this time the PowerBuilder DirectConnect interface is NOT intended to support connections to the Transaction Router Service (TRS) or any other service on the DirectConnect server. Additional services will be supported in PowerBuilder 7.0.

DataWindow Synchronization
--------------------------
The set of DataWindow Synchronization features which deal with multiple sources and targets as described in the documentation is not supported in this release. The supported configurations are: 
- single source, single target for update
- single source, multiple target for read-only (broadcast)

The return value of the DataWindow Synchronization GetChanges() function is not reliable when used with the optional cookie parameter.

Distributed PowerBuilder Components
-----------------------------------
If you used Distributed PowerBuilder with PowerBuilder 5.0, you will notice a couple of changes.  Most Distributed PowerBuilder functionality has been incorporated into the deployment DLLs; therefore, when you install PowerBuilder on a client machine, you have the software necessary to use Distributed PowerBuilder from that client. 

Also, we found that few people used the Open Client/Open Server driver with Distributed PB, so have dropped that driver for PowerBuilder 6.0. We continue to support Winsock and Named Pipes drivers.

Fewer DLLs /Libraries
---------------------
There are fewer DLLs (libraries on non-Wintel platforms) than there used to be for PowerBuilder. Functionality has been combined, and you can now deploy an application with as few as 1 DLL (PBVM60.DLL), but realistically, you'll probably use three ... PBVM60.DLL, PBDWE60.DLL (for DataWindow functionality) and one DLL for whichever database you are using.

Installing on NT4.0
-------------------