PFC 6.5.00 Changes

PowerBuilder Foundation Class Library Version 6.5

RELEASE NOTES

*****************************************************************
* *
* Welcome to PFC Version 6.5 for PowerBuilder. *
* *
*****************************************************************

Copyright © 1996-1998 Sybase, Inc. and its subsidiaries. All rights reserved.

Please take a few minutes to review this file for changes and bug fixes
that have been made to the libraries.

Contents of this file:
=====================
New Libraries
New Extension Objects
New Syntax
Obsolete Library
Migration Notes
Changes and Bugs Fixed

=================================================================
NEW LIBRARIES
=================================================================
PFC 6.0 contains two new libraries for utility-oriented services:
PFCUTIL.PBL
PFEUTIL.PBL

Both existing and new PFC applications should include these libraries
in their application paths.

The following PFE-level objects from prior versions of PFC have been
moved to PFEUTIL.PBL. If you have existing applications with customized
extension PBLs, you may wish to synchronize their contents with the
object list found in PFEUTIL.PBL. This is not required.

The following objects were moved to PFEUTIL.PBL:
n_cst_debug
n_cst_sqlspy
w_debuglog
w_sqlspy
w_sqlspyinspect

=================================================================
NEW EXTENSION OBJECTS (there are no new objects for 6.5)
=================================================================
These extension objects should be included in your customized
extension PBLs. The object name, PowerBuilder library, and
release are listed for each new extension object.
For more information or help on retaining customizations to your
extension levels when upgrading to a new release of PFC, please
refer to Powersoft Faxline #4505.

Note: this step is only necessary for migrating existing PFC
applications to a newer version of PFC.

5.0.02 n_cst_filesrvmac pfeapsrv.pbl
5.0.02 n_cst_filesrvsol2 pfeapsrv.pbl
5.0.02 n_cst_platformmac pfeapsrv.pbl
5.0.02 n_cst_platformsol2 pfeapsrv.pbl
5.0.02 w_print pfeapsrv.pbl

6.0 n_cst_apppreference pfeapsrv.pbl
6.0 n_cst_color pfeapsrv.pbl
6.0 n_cst_columnattrib pfeapsrv.pbl
6.0 n_cst_dberrorattrib pfeapsrv.pbl
6.0 n_cst_dropdown pfeapsrv.pbl
6.0 n_cst_filesrvaix pfeapsrv.pbl
6.0 n_cst_filesrvhpux pfeapsrv.pbl
6.0 n_cst_infoattrib pfeapsrv.pbl
6.0 n_cst_linkedlistbase pfeapsrv.pbl
6.0 n_cst_linkedlistnode pfeapsrv.pbl
6.0 n_cst_linkedlistnodecompare pfeapsrv.pbl
6.0 n_cst_list pfeapsrv.pbl
6.0 n_cst_luw pfeapsrv.pbl
6.0 n_cst_lvsrv pfeapsrv.pbl
6.0 n_cst_lvsrv_datasource pfeapsrv.bpl
6.0 n_cst_lvsrv_sort pfeapsrv.pbl
6.0 n_cst_lvsrvattrib pfeapsrv.pbl
6.0 n_cst_metaclass pfeapsrv.pbl
6.0 n_cst_mru pfeapsrv.pbl
6.0 n_cst_mruattrib pfeapsrv.pbl
6.0 n_cst_nodebase pfeapsrv.pbl
6.0 n_cst_nodecomparebase pfeapsrv.pbl
6.0 n_cst_platformaix pfeapsrv.pbl
6.0 n_cst_platformhpux pfeapsrv.pbl
6.0 n_cst_queue pfeapsrv.pbl
6.0 n_cst_stack pfeapsrv.pbl
6.0 n_cst_tmgmultiple pfeapsrv.pbl
6.0 n_cst_tmgregisterattrib pfeapsrv.pbl
6.0 n_cst_tmgsingle pfeapsrv.pbl
6.0 n_cst_tree pfeapsrv.pbl
6.0 n_cst_treenode pfeapsrv.pbl
6.0 n_cst_treenodecompare pfeapsrv.pbl
6.0 n_cst_tvsrv pfeapsrv.pbl
6.0 n_cst_tvsrv_levelsource pfeapsrv.pbl
6.0 n_cst_tvsrv_print pfeapsrv.pbl
6.0 n_cst_tvsrvattrib pfeapsrv.pbl

6.0 n_cst_dssrv_multitable pfedwsrv.pbl
6.0 n_cst_dssrv_printpreview pfedwsrv.pbl
6.0 n_cst_dssrv_report pfedwsrv.pbl
6.0 n_cst_dwsrv_resize pfedwsrv.pbl
6.0 n_cst_restorerowattrib pfedwsrv.pbl
6.0 w_restorerow pfedwsrv.pbl

6.0 m_lvs pfemain.pbl
6.0 m_tvs pfemain.pbl
6.0 n_base pfemain.pbl
6.0 n_cst_baseattrib pfemain.pbl
6.0 n_cst_calculatorattrib pfemain.pbl
6.0 n_cst_calendarattrib pfemain.pbl
6.0 n_cxinfo pfemain.pbl
6.0 n_cxk pfemain.pbl
6.0 n_dda pfemain.pbl
6.0 n_dsa pfemain.pbl
6.0 n_inet pfemain.pbl
6.0 n_ir pfemain.pbl
6.0 n_oo pfemain.pbl
6.0 n_ostg pfemain.pbl
6.0 n_ostm pfemain.pbl
6.0 n_srv pfemain.pbl
6.0 n_tmg pfemain.pbl
6.0 u_base pfemain.pbl
6.0 u_calculator pfemain.pbl
6.0 u_calendar pfemain.pbl
6.0 u_lvs pfemain.pbl
6.0 u_progressbar pfemain.pbl
6.0 u_st_splitbar pfemain.pbl
6.0 u_tvs pfemain.pbl

6.0 *n_cst_dwpropertyattrib pfeutil.pbl
6.0 *n_cst_dwsrv_property pfeutil.pbl
6.0 *n_cst_propertyattrib pfeutil.pbl
6.0 *u_tab_dwproperty pfeutil.pbl
6.0 *u_tab_dwproperty_srv pfeutil.pbl
6.0 *u_tabpg_dwproperty_base pfeutil.pbl
6.0 *u_tabpg_dwproperty_buffers pfeutil.pbl
6.0 *u_tabpg_dwproperty_services pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvcalculator pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvcalendar pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvcalendar2 pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvdropdownsearch pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvfilter pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvfind pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvlinkage pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvlinkage2 pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvmultitable pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvprintpreview pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvquerymode pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvreport pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvreqcolumn pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvresize pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvrowmanager pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvrowselection pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvsort pfeutil.pbl
6.0 *u_tabpg_dwproperty_srvsyntax pfeutil.pbl
6.0 *u_tabpg_dwproperty_status pfeutil.pbl
6.0 *w_dwproperty pfeutil.pbl
6.0 *w_dwpropertyservices pfeutil.pbl

* = these objects are in a new PFC PBL. No action should be required
to incorporate these objects into existing customized extension libraries
as long as you will be including PFEUTIL.PBL in your application path.

=================================================================
NEW SYNTAX
=================================================================
There has been new syntax added to PFC for consistency, ease of use
in the product, and new functionality. Some existing syntax has been
"obsoleted" in favor of the new syntax. This syntax will be removed from
PFC in a future version of the product.

Old syntax New syntax
---------- ----------
all prefixed constants CAPS and non-prefixed
pfc_n_cst_dwsrv
of_GetColumnNameSource of_GetColumnDisplayNameStyle
of_SetColumnNameSource of_SetColumnDisplayNameStyle
of_RefreshDDDWs of_PopulateDDDWs
pfc_n_cst_dwsrv_linkage
of_SetUpdateBottomUp of_SetUpdateStyle
of_GetUpdateBottomUp of_GetUpdateStyle
of_SetUseColLinks of_SetStyle
of_GetUseColLinks of_GetStyle
of_GetValue
of_SetArguments of_Register
of_ResetArguments of_UnRegister
of_GetArguments of_GetRegistered
of_LinkTo of_SetMaster
of_UnLink of_ResetMaster
ib_updatebottomup ii_updatestyle
pfc_n_cst_dwsrv_dropdownsearch
of_AddColumn of_Register
of_GetColumn of_GetRegistered
pfc_n_cst_dwsrv_multitable
of_AddToUpdate of_Register
pfc_n_cst_security
of_GetType
of_FindEntry
of_GetTag
of_ScanDataWindow
of_InitScanProcess
of_ScanWindow
of_AddObject
of_ScanControlArray
pfc_u_dw
pfc_retrievedddw pfc_populatedddw
of_GetUpdateable of_IsUpdateable
pfc_n_cst_datetime
of_DayofWeek DayNumber
pfc_w_dwdebugger pfc_w_dwproperty
pfc_w_undelete pfc_w_restorerow

=================================================================
OBSOLETE LIBRARY
=================================================================
PFCOLD.PBL contains objects which have been obsoleted from PFC.
You will need to include it when migrating PFC applications to PFC 6.0.

After your existing PFC apps have been migrated, it is only necessary
to include this library if you have customized extension objects which
depend on it.

Note that all obsoleted objects do have replacement objects.

=================================================================
MIGRATION NOTES
=================================================================
PFC 6.0 introduced events mapped to the standard event IDs. If you have declared
user events in descendants of these objects and mapped them to the same IDs
problems may be encountered when migrating from PFC 5.0 applications.
New events are:
pfc_u_dw - dropdown - pbm_dwndropdown
pfc_u_base - resize - pbm_size

Please refer to the Faxline Migration document if you need further assistance
migrating PFC 5.0 applications to PFC 6.0.

=================================================================
CHANGES AND BUGS FIXED
=================================================================

Debug Services
--------------
Object: d_debuglog, pfc_n_cst_sqlspy
Method:
Fix: Added Century to date format
Tech support#: 497810

String Service
--------------
Object: pfc_n_cst_string
Method: of_getkeyvalues
Fix: Corrected to make sure that the keyword is a standalone word instead of a portion of a
word
Tech support#: 452691

DateTime Service
----------------
Object: pfc_n_cst_datetime
Method: of_IsValid(date)
Fix: Remove comparison to invalid date. Previously, 1-1-1900 was being returned as an
invalid date but in reality it is a valid date. Thus doing an of_isvalid of a valid
date of 1-1-1900 would be returned as invalid (false).
Tech support#: 497810

Message/Error Service
---------------------
Object: pfc_n_cst_error
Method: of_message
Fix: Removed unwanted beep(1) call
Tech support#: 490782

Timing Service
--------------
Object: pfc_n_cst_tmgsingle
Method:
Fix: Removed instance variable reference to the n_cst_datetime object.
Tech support#: 498664

Transaction Registration Service
--------------------------------
Object: pfc_n_cst_trregistration
Method: Destructor
Fix: Enhanced code so that different behaviors can be performed when destroying the service.
Tech support#:

File Service
------------
Object: pfc_n_cst_filesrv
Method: of_sortdirlist
Fix: Destroy local datastore explicitly
Tech support#:

Object: pfc_n_cst_filesrv
Method: pfc_n_cst_filesrvwin32, pfc_n_cst_filesrvsol2, pfc_n_cst_filesrvmac,
of_convertpbdatetimetofile
Fix: Corrected milisecond formatting which caused overflow of millisecond uint.
Tech support#: 423591

Object: pfc_n_cst_filesrv
Method: of_filewrite
Fix: Correct to handle writing of strings > 60k.
Tech support#: 489023

Object: pfc_n_cst_filesrvaix, pfc_n_cst_filesrvhpux
Method: of_convertpbdatetimetofile
Fix: Corrected milisecond formatting which caused overflow of millisecond uint.
Tech support#: 423591

Dropdown service
----------------
Object: pfc_n_cst_dropdown
Method: of_Position
Fix: Corrected issues dealing with DataWindow Group Headers and Trailers.
Tech support#:

PFC Treeview
------------
Object: pfc_u_tv, pfc_n_cst_tvsrv
Method: of_finditem, of_searchchild, of_findfirstitem
Fix: Rewrote of_finditem, of_searchchild, of_findfirstitem to be non-recursive.
Recursive logic was causing GPF's on trees with 50+ items on win16 platform.
Tech support#: 477984, 437966, 361483, 473371, 465619, 457014, 455714, 451537,
440876, 413306, 411618

Object: pfc_u_tv
Method: of_refreshitem
Fix: Fix return code to return 1 on success, not 0
Tech support#: 377319

Object: pfc_u_tv
Method: of_SetDatasource
Fix: of_SetDatasource returns error condition on following conditions:
labelcolumn does not exist or not string(-4);
settransobject failure (-5)
Tech support#: 426572

Object: pfc_u_tv
Method: of_PopulateLevel
Fix: of_PopulateLevel return code checking:
settransobject (-5);
retrieve (-3);
updateable dw (-4);
label column creation (-2)
Tech support#: 426567, 371950

Object: pfc_u_tv
Method:
Fix: Change code for Datastore's SetTransObject to use PFC of_SetTransobject function
Tech support#: 426567

PFC Listview
------------
Object: pfc_u_lv
Method: of_deletecolumns
Fix: Add check to see if there are columns to delete
Tech support#: 449985

Object: pfc_u_lv
Method:
Fix: Change code for Datastore's SetTransObject to use PFC of_SetTransobject function
Tech support#: 426567

PFC Windows
-----------
Object: pfc_w_master
Method: CloseQuery event
Fix: Corrected so that window is not hidden prior to displaying a closequery message
Tech support#: 473364

Object: pfc_w_splash, pfc_w_logon, pfc_w_about
Method:
Fix: Corrected so that if there is no application logo the picture control will be made
invisible
Tech support#: 460506

PFC Menus
---------
Object: pfc_m_master
Method:
Fix: Corrected minimize all functionality which left all other window positioning
menu items permantly disabled.
Tech support#: 473367

PFC Editmask
------------
Object: pfc_u_em
Method: of_SetDropDownCalculator and of_SetDropDownCalendar
Fix: Corrected so as to tell the object to behave as a dropdown object.
Tech support#: 499227

Object: pfc_u_em
Method: of_SetDropDownCalculator and of_SetDropDownCalendar
Fix: Enhanced so that the message object information is not lost when an
OpenUserObject function is executed.
Tech support#: 486438

PFC Message object
------------------
Object: pfc_n_msg
Method:
Fix: of_CopyTo, of_Get/of_Set, and instance variables added. This was done to allow fixes
in other places dealing with the message object being owerwritten.
Tech support#:

PFC DataWindow
--------------
Object: pfc_u_dw
Method: pfc_print
Fix: Destroy local datastore prior to returning under error condition
Tech support#: 488591

Object: pfc_u_dw
Method: rbuttonup
Fix: script caused 64K segment problem when compiling to 16bit machine code
Tech support#: 425448

Object: pfc_u_dw
Method: rbuttonup
Fix: Corrected so that dwo.protect works properly for protect expressions.
The Cut and Copy on the PopUp menu now work with protect expression.
Tech support#: 498701

Object: pfc_u_dw
Method: of_Retrieve
Fix: Corrected function return type from integer to long.
Tech support#: 494086

Object: pfc_u_dw
Method: rbuttonup
Fix: Isolated calls to the shared variable snv_property. This allows for
regular overriding of the rbuttonup event.
Tech support#: 498692

Object: pfc_u_dw
Method: of_SetDropDownCalculator and of_SetDropDownCalendar
Fix: Enhanced so that the message object information is not lost when an
OpenUserObject function is executed.
Tech support#: 486438

Object: pfc_u_dw
Method: of_CheckRequired and pfc_checkrequirederror
Fix: Allow options to better handle customization without having to override
the entire function.
Tech support#: 473361

DataWindow PrintPreview Service
-------------------------------
Object: pfc_n_cst_dwsrv_printpreview, pfc_n_cst_dssrv_printpreview
Method: of_SetEnabled
Fix: Corrected by adding check to prevent error condition when datawindow is nested
Tech support#: 401957

DataWindow Linkage Service
--------------------------
Object: pfc_n_cst_dwsrv_linkage
Method: of_Retrieve
Fix: Corrected so that when appropriate scrolling occurs to the desired row
after a retrieve
Tech support#: 490794

Object: pfc_n_cst_dwsrv_linkage
Method: of_retrieveDetails
Fix: Corrected so that the return code of an internal PowerScript retrieve call is captured
by a long type variable.
Tech support#: 495410

DataWindow Base Service
-----------------------
Object: pfc_n_cst_dwsrv & pfc_n_cst_dssrv
Method: of_setitem
Fix: Correct where number and real datatypes were being converted into long datatypes
Tech support#: 432602

Object: pfc_n_cst_dwsrv & pfc_n_cst_dssrv
Method: of_GetItem
Fix: Corrected so that LookUpDisplay values for DropDownListBoxes are handled. Computed
fields
expressions were also improved.
Tech support#: 468405

8-) ~~ Special thanks to Ken Kellis, Lijun Yang, Jerry Metz, Rodney Mohr, Ian Ross, Rick Seeley, Irene Troupansky, Oliver Willandsen, Cecil Owens, Ravi Sathyanarayana for passing this along to us

[Back to Top] [Sybase Contacts]

What's New in PB 6.5 ?

[PB (vs. PFC) 6.5 Release Notes (Below)]
[PB 6.5 Get/SetFullState Workarounds]
[How to fix AutoInstantiated Objects]
[Sybase Downloads]

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
-------------------
You must have Administrator privileges to fully install this product on NT 4.0.

InstallShield
-------------
InstallShield 5.0 Free is included with PowerBuilder for Windows. IS5Free can be used to build
installable files for your PowerBuilder applications.

Internet Explorer 4.0
---------------------
At the time PB 6.0 was released, Microsoft IE 4.0 had just been released and some compatibility
issues with PowerBuilder 6.0 were identified, but it was too late to correct them. Those issues
have been resolved in PB 6.5.

Migration Information
---------------------
Please read the Technical Migration Document in the \Support directory on the CD to see what
behavior changes you can expect to see in PowerBuilder 6.0. This document is updated with every
release candidate, and also includes information on migrating from PowerBuilder 4.0.

Online Books
------------
Online Books are now available over the web! The URL for the DynaWeb version of the PB6 and
IM6 online books is: http://calas.sybase.com.
This URL is also available under the PowerBuilder and InfoMaker Help menus.

OLE Synchronization DLLs
------------------------
Some customers have been experiencing OLE problems due to mis-matched OLE DLLs. OLE32.DLL must
be dated 1/26/97 - if you have an older version, you will experience problems. To get the
update, you may have to reinstall the OS and upgrade with appropriate MS OS service packs.
Also the DLL rpcrt4.dll must be kept in sync with ole32.dll.

Third Party Vendors using ORCA
------------------------------
The following files may be found in the ORCA folder on the CD:

pbtapi.h
pborca.h
pborca.lib

Silent Install
--------------
On the Windows platform, you can create a "silent" install for PowerBuilder - one which can be
set up and run without user intervention. This is handy for system administrators. See the
documentation (Deploying your Application in Application Techniques) for further information.

DataWindow Scrollbar Operation
------------------------------
When scrolling through certain groups, two of the same Group Header with subsets of the group,
re-displayed on the screen. The scrollbar operation for DataWindows was changed in 6.0. The
virtual scrolling enhancement allows any row to be at the top of a screen view (even in a group
dw), and print preview scrolling to scroll from the top of the report to the bottom of the
report, all in one slide. This means that it is possible to scroll to a point that shows the
bottom half of one page and the top half of the next page. If the arrow keys or the page
up/down keys are used exclusively, then the issue does not arise. The scrollbar enhancement
was added to override the navigation keys in browser context.

PBWEB.INI Cannot be found
-------------------------
The message "c:\Windows\PBWEB.INI" cannot be found is caused by an incorrect file location. The
PBWEB.INI should be moved from the ..\sybase\pb6\it directory to your system directory (e.g.
c:\windows).

Application path for sample
---------------------------
The application path for the niexample is incorrect. Use the application to correct the pbl
name. The correct name is niexdpbs.pbl (typically located in ..\sybase\pb6\appgal\javasamp).

Localized Deployment Kits
-------------------------
The localized deployment kits cannot be installed directly from the PowerBuilder 6.5 install.
You will need to navigate to the Ldddk16 or Ldddk32 folder on the PowerBuilder 6.5 CD and run
setup.exe from there.

On a 16-bit machine, the English 16-bit deployment kit must be installed from setup.exe in the
Dddk16 folder on the PowerBuilder 6.5 CD.

==================================================
Section II: PowerBuilder Documentation Addendum
==================================================

This section contains information and known Documentation errors in the books shipped with
PowerBuilder 6.0.x

Building Internet Applications with PowerBuilder
------------------------------------------------
Chapter 9 of the Building Internet Applications with PowerBuilder
manual incorrectly states that Microsoft Internet Explorer requires
the NCompass ScriptActive plug-in. It is Netscape Navigator that
requires the NCompass ScriptActive plug-in.

This has been fixed in the online Help and the online books but is incorrect in the hardcopy
book.

Chapter 9 of the Building Internet Applications with PowerBuilder
manual provides an incorrect list of modules required by the
PowerBuilder window ActiveX. The correct list is:
- mfc42.dll
- msvc42.dll
- url.dll
- urlmon.dll
This has been fixed in the online Help and the online books but is incorrect in the hardcopy
book.

Also, to use VBScript with the PowerBuilder window ActiveX, you need
Version 2.0 (or higher) of vbscript.dll.

PowerBuilder 6.0 User's Guide
-----------------------------
Chapter 18 of the PB 6.0 User's Guide provides inaccurate information about deploying an
application to a user's machine. It says: "Setup installs the components you selected. By
default, Setup installs system DLLs in the appropriate system directory for your operating
system, prompting you for an action if an update fails".

In the case of the deployment kit, we install the components under a directory called DDDK6 so
that they are easily identifiable, rather than to the system directory.

PFC Object Reference
--------------------
The following objects were not documented in the PFC Object Reference:
- n_cst_mru
- n_cst_tmgmultiple
- n_cst_tmgsingle
- n_cst_linkedlistbase
- n_cst_linkedlistnode
- n_cst_linkedlistnodecompare
- n_cst_list
- n_cst_nodecomparebase
- n_cst_nodebase
- n_cst_queue
- n_cst_tree
- n_cst_treenode
- n_cst_treenodecompare

These objects are documented in the online Help and on the Powersoft Documentation web site.

In the printed PFC Object Reference, the function and event lists for the following objects are
incorrect:
- u_lvs
- n_cst_lvsrv_datasource
- n_cst_tvsrv_levelsource

The function and event lists in the online Help and on the Powersoft Documentation web site are
correct.
**********************************************************************
(c) 1991-1998 Sybase, Inc. and its subsidiaries. All rights reserved. Sybase, Inc. and its
subsidiaries ("Sybase") claim copyright in this Program and documentation as an unpublished
work, versions of which were first licensed on the date indicated in the foregoing notice.
Claim of copyright does not imply waiver of Sybase's other rights. See Notice of Proprietary
Rights.

NOTICE OF PROPRIETARY RIGHTS
This computer program and documentation are confidential trade secrets and the property of
Sybase, Inc. and its subsidiaries. Use, examination, reproduction, copying, disassembly,
decompilation, transfer and/or disclosure to others, in whole or in part, are strictly
prohibited except with the express prior written consent of Sybase, Inc. and its subsidiaries.

8-) ~~ Special thanks to Ken Kellis, Lijun Yang, Jerry Metz, Rodney Mohr, Ian Ross, Rick Seeley, Irene Troupansky, Oliver Willandsen, Cecil Owens, Ravi Sathyanarayana for passing this along to us

[Back to Top] [Sybase Downloads]

Home

Know where to go

Work smarter, not harder

Answers at your fingertips

What's New in PFC 6.5 ?

[PB (vs. PFC) 6.5 Release Notes (Below)]
[PB 6.5 Get/SetFullState Workarounds]
[How to fix AutoInstantiated Objects]
[Sybase Downloads]

[Back to Top] [Sybase Contacts]

What's New in PB 6.5 ?

[PB (vs. PFC) 6.5 Release Notes (Below)]
[PB 6.5 Get/SetFullState Workarounds]
[How to fix AutoInstantiated Objects]
[Sybase Downloads]

[Back to Top] [Sybase Downloads]

Home | Top

What's New in PFC 6.5 ?

[PB (vs. PFC) 6.5 Release Notes (Below)] [PB 6.5 Get/SetFullState Workarounds] [How to fix AutoInstantiated Objects] [Sybase Downloads]

[Back to Top] [Sybase Contacts]

What's New in PB 6.5 ?

[PB (vs. PFC) 6.5 Release Notes (Below)] [PB 6.5 Get/SetFullState Workarounds] [How to fix AutoInstantiated Objects] [Sybase Downloads]

[Back to Top] [Sybase Downloads]

Home | Top

[PB (vs. PFC) 6.5 Release Notes (Below)]
[PB 6.5 Get/SetFullState Workarounds]
[How to fix AutoInstantiated Objects]
[Sybase Downloads]

[PB (vs. PFC) 6.5 Release Notes (Below)]
[PB 6.5 Get/SetFullState Workarounds]
[How to fix AutoInstantiated Objects]
[Sybase Downloads]