Release Notes for

PowerBuilder[TM] Enterprise Version 5.0.02
PowerBuilder[TM] Professional Version 5.0.02
PowerBuilder[TM] Desktop Version 5.0.02

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

Updated 11/8/96

***********************************************************************

General Information
-----------------------

Windows NT 4.0

PowerBuilder 5.0 has been tested on the production release of 
NT 4.0 build 1381 and Service Pack 1.  Some painting issues have
been identified and reported that are specific to PowerBuilder
and InfoMaker running on this platform.  See the Known Anomalies
in PowerBuilder 5.0.02 section of this release note.

No other known platform-specific issues exist at this time, and
we believe that most customer applications will run correctly. 
If you find any anomalies with PowerBuilder or InfoMaker 
performance on Windows NT 4.0, please report them immediately.


Installation
------------
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 setup32.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.

Installation/Uninstall Problems on Windows NT 4.0

There are known problems with the PowerBuilder installation 
program having white backgrounds when run under Windows NT 4.0.
This will be corrected in a future release of PowerBuilder and
InfoMaker.

Uninstall does not work on Windows NT 4.0.  Users who need
to remove PowerBuilder machine must manually delete Powersoft
file and registry entries.


General Uninstall Issues
-------------------------------
When you run an Uninstall for PowerBuilder 5.0 or InfoMaker 5.0 on 
Windows 95, it will leave a DOS session called DELETEME in the 
TaskBar.  Just close the DOS session to complete deletion of all 
files.

Uninstall was designed to completely delete PowerBuilder and its
components from your system.  It is not able to selectively delete
patches.  Installing Maintenance patches, e.g., PB 5.0.01 Fixes 
or PB 5.0.02 Fixes, completely updates PowerBuilder with a new
set of dll's.  So, therefore, choosing to uninstall PB 5.0.01 fixes 
will effectively delete all the PowerBuilder dll's, and make your
PB software unusable.


Setup and CTL3D32.DLL
----------------------
On Win95 and WinNT, you may receive a message that there is an invalid 
version of ctl3d32.dll on your system.  You can press OK, and Setup 
will run normally; however the colors may be splotched, and the UI may 
not look as intended.

This happens because there are different versions of Ctl3d32.dll for 
Windows95 and WindowsNT.   Setup tries to install the correct version 
on your system, but this may fail if an invalid version was installed 
by another application.

To solve, exit setup.  Search your system for ctl3d32.dll, and rename 
any other instances to ctl3d32.old.  Upon running Setup again, Setup 
will install the correct version and run normally.

Installing PowerBuilder on a Network drive
-----------------------------------------
32-bit only:
If you have installed PowerBuilder on a network, each client machine
that will be using PB will need to make some local Registry in order
to run machine. To make these entries, locate the Support\netinst 
directory and run Setup on each client machine.

This will run the PB Local Setup for Network Install, and create
the entries you need.   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 Powersoft Demo Database - This is the path to the Demo 
   Database used on initial InfoMaker startup.
	WinNT default: pwrs\pb5i32\
	Win95 default: Program Files\Powersoft\PowerBuilder 5.0\

Continue with the install normally.  When the install finishes, you 
should have a program item for PowerBuilder, SQLAnywhere, the Demo 
Database and Uninstall on the local machine.

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 Installation Guide".


Online Books Install
--------------------
The install for the Online Books will give you the choice of Typical,
Compact and Custom installs, but there is only one small viewer 
loaded, and no difference between what is installed under the 3 
options.


Component Installation
----------------------
Visual Components First Impression v2.0 (VCFI32.OCX) is copied to the Component 
Gallery directory (usually \pwrs\compglry or \program files\powersoft\component 
gallery) if the Application Gallery, Code Examples or Component Gallery options 
are selected for installation. Typically components are registered  by the Setup 
program. Version 2.0 of First Impression does not properly support the DllRegisterServer 
function and silently fails to register. You should manually register this control 
using PowerBuilder or REGSVR32.EXE. This problem has been corrected in First Impression 2.1.

To register an .OCX with PowerBuilder:
1) Select the OLE object in the window painter.
2) In the Insert Object Dialog, select the Insert Control Tab
3) Insert Control Tab: select Register New
4) Then select the OCX filename to register in the Browse file dialog.
(i.e. C:\PWRS\CompGlry\VCFI32.ocx)

To register an .OCX with REGSVR32:
1) Type regsvr32 <filename>

Upon registering the control you will receive the message "VCFI32.OCX is not marked 
as supporting self registration. However the function DLLRegisterServer was found. Do 
you wish to register?"

      Click OK and it will register properly.


"PB050.EXE App-error.  The app failed to initialize properly" error 
----------------------------------------------------------------------------------

"PB050.EXE App-error.  The app failed to initialize properly" error 
when attempting to first start PowerBuilder.

This problem has once been seen on Windows NT 3.51 using long filenames.

Double clicking the PowerBuilder icon results in this error.  The Program manager of
Windows NT has failed to properly setup the PowerBuilder ICON.  to resolve the problem,
create a new ICON for PowerBuilder (using the Browser from the Program manager) to set
the executable for PowerBuilder and the working directory path.  this is normally:

c:\Program Files\Powersoft\PowerBuilder 5.0\PB050.EXE
and
c:\Program Files\Common Files\Powersoft Shared

Once the new ICON is setup, the original may be deleted.

Troublshooting tips when attempting to use help from the preview painter.
---------------------------------------------------------------------------

On some Windows 16 systems, windows help is  unable to locate the help file 
PBHLP050.HLP from the Data Window preview painter.  This results in the error 
"unable to open help file".  to alleviate this problem, COPY PBHLP050.HLP from 
c:\pwrs\pb5\sys to c:\pwrs\sys.  


Troubleshooting Tips for Database Connections
--------------------------------------------- 
Follow these directions if you get IM003 or IM004 errors 
connecting to a database (including starting up InfoMaker for 
the first time).

These errors occur for a variety of reasons, but the basic cause 
is that the database engine components are not found by the 
application.  To fix, in Windows 3.x and Windows 95, you can add 
the database engine directory to your DOS path (for example, 
C:\SQLANY50\WIN32).

In Windows95, you can add it to the Registry AppPath for the 
executable.  For example, to add to the AppPath for InfoMaker 
(IM050.exe), look for the following entry in the Registry: 
HKEY_LOCAL_MACHINE/ SOFTWARE/Microsoft/Windows/Current Version/App Paths
/IM050.exe

Double-click on Path icon and add a semi-colon and the fully 
qualified path to the entry.

On NT, use Control Panel/System to edit your system path to add the 
appropriate pathing information.

The SQLANY environment variable (if exists) must point to the proper 
SQLANY50 directory (e.g. "C:\SQLANY50").  

On Windows or Windows 95, this is set in Autoexec.bat.

On NT,use Control panel/system to edit this variable.


New Database Drivers in 5.0.02
------------------------------
If you are installing either of the two new database drivers from the
the 5.0.02 Maintenance CD (ORACLE v7.3 and INFORMIX v7.x), you will have
to add them manually to the vendors list section in your pb.ini or im.ini 
file.


MKS Source Integrity Interface
------------------------------
PBE Release 5.0.02 includes a native source control interface for MKS 
Source Integrity on both 16bit and 32bit platforms.  PBRCS050 has been 
certified using release 7.1c of MKS Source Integrity.  Complete documentation 
regarding its use is found in Chapter 5 of the PowerBuilder 5.0 manual 
entitled "Version Control Interfaces".

Ptrack issue 370134 has NOT been fixed on this maintenance release.  This 
deals with the use of substitution parameters in the RCSPATH= entry of a 
RCS configuration file.  For this release, do NOT use  RCSPATH=%v%d\rcs\%f  
to specify an archive directory.  Rather, use an explicit drive and path 
specification.  The example below shows how to list multiple archive 
directories:
	RCSPATH=c:\myproj\rcs;c:\anotherproj\rcs

A fix for issue 370134  is currently being evaluated.  It will be available 
for download from our web site and BBS as soon as it is certified.


Data Express Help File on NT 3.51
---------------------------------
If you are running under Windows NT 3.51, the Data Express program will not
be able to find its Help file unless you add the location of that help file
to the system path.  The help file is found in the PB5i32\Sys32 subdirectory,
unless you have installed PowerBuilder in some other directory.  For a default
installation using short filenames, you would need to add "pwrs\pb5i32\sys32"
to your system path, accessed via ControlPanel->System.


Latest Sybase SQLAnywhere release
---------------------------------
This CD contains release 5.03 of Sybase SQLAnywhere.


Keyword "this" in Global Functions No Longer Valid
--------------------------------------------------
You can no longer use the keyword 'this' in a global function.  Versions 5.0.0 
and earlier allowed you to do this, returning the classname of the object that 
called the global function.   This behavior was incorrect and has been changed 
in version 5.0.02.   Although this usage is not flagged as an error by the 
compiler in this version, it will cause a null object reference at runtime.   
Applications taking advantage of this old behavior must be modified.


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.


16-bit Machine Code Excecutables
---------------------------------
Fixes to problems with 16-bit machine code executables have made it
necessary for ALL 16-bit machine code executables to built using
DLL's.  Previous executables should be rebuilt using this 
configuration.


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.


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.


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.


Producing Execution Diagnostics from the Development Environment
--------------------------------------------------------------
A facility to generate a diagnostic trace of PB application execution 
is now available in the PB development environment. This feature 
produces the same diagnostic trace as the /PBDebug switch used from 
PowerBuilder generated executables. To turn the trace on, add the 
following entries to the [pb] section of your PB.INI file. 

DebugOutFile=<Output File Path>
PBDebug=<on -or- off>

Where:

<Output File Path> is the full pathname of the file that you want 
the diagnostic output to go to. If the DebugOutFile variable is 
omitted, PBDebug creates an output file with the name "PB050.DBG" 
in the same directory as the PB050.EXE file. 

<on -or- off> is either the value "on" or "off". Setting PBDebug 
to "on" invokes the trace.

Example:
To turn PBDebug on and send its trace output to a file on the 
"temp" directory, add the following variables to PB.INI:

[pb]
DebugOutFile=c:\temp\pb.dbg
PBDebug=on

Notes:
Running diagnostics will make PB slow down considerably. Be sure 
to turn the PBDebug variable to off when you are through with it.

You must supply a full pathname for <Output File Path>. If you 
don't, you may lose some of  your diagnostic output. 

Each time the PB development environment runs with PBDebug on, 
the trace file is overwritten. It is important to rename the 
trace file between runs if you wish to save its data. 

A long session with PBDebug turned on can produce a rather large 
trace file. If you run for a long time with PBDebug on, be sure 
to have enough disk space for the trace file.


Known Anomalies in PowerBuilder 5.0 FIXED in 5.0.02
---------------------------------------------------
Please refer to the file 502fixes.wri, located at the root of the
CD, for a list of bugs fixed in the 5.0.02 release.  For a complete
list of fixes, please refer to the TechBull.nfo, also located at
the root of the CD.


Upgrading from PowerBuilder 4.0
-------------------------------
If you are installing the PowerBuilder update (which requires either 
an installed prior version of PowerBuilder, or the CD or diskette 
from a prior version), you will be able to use diskettes from 
PowerBuilder 1, 2, and 3, but cannot use a diskette from 
PowerBuilder 4.0; you must use the CD or installed version.


Pipeline SQLAnywhere to Informix 5
----------------------------------
Columns defined in SQLAnywhere as char are being piped to Informix datatype
of nvarchar. If the database does not have NLS (National Language Support)
activated, you will get a SQL -201 error: a syntax error has occurred. 
Workaround: If you change the nvarchar to varchar, the table will pipe. 


NVARCHAR on Informix
--------------------
PowerBuilder documentation does not indicate that we support nvarchar and
nchar in Informix,although they show up as a choice in table painter for
datatypes. I could not create a tablein IN5 using INET 5.01TE1 with a 
nvarchar column: got the same -201 error. In 16-bit, same problem using 
INET 5.01WF1. I did not test with a database with NLS installed to see if it 
would work there.


PB5 O72 Interface
-----------------
PB5 Oracle O72 interface to Oracle 7.2.2.0 database: 
Executing a stored procedure which has a result set: get ora-01023 
"Cursor context not found(Invalid cursor number)" when procedure is 
executed. Trace indicates that the error comes on Get Number of Columns 
Selected.

Connected to Oracle 7.3 database with o73 or o72, get message 
"Invalid stored procedure parameter mode of 'IN OUT' on ", 
please change to either 'IN' or 'OUT'": this is immediately on the 
execute,before it tries to Get Number of Rows. Also get this message
connected to Oracle 7.2.3.0.0 with O72.


RTE Control on Windows NT4
--------------------------
On NT4.0 the Rich Text Edit window control when resized will leave a
trail of it's previous sizes. When you run the window with the Rich 
Text Edit control on it the background will bleed through and appear 
to be in the Rich Text Edit control.  Even when you close the window
and go back to the development environment the backgound still appears
in the control.  If you insert a file into the Rich Text Edit control
the background does not bleed through.


Access Rights Keywords
----------------------
Grouping of the PrivateRead, PrivateWrite, ProtectedRead, 
ProtectedWrite keywords does not work as described in the PowerScript 
Language Reference.  These keywords currently do not work when 
grouped with the access right keyword as a label.  Attempting to 
group these keywords causes compiler Syntax errors.  The PowerBuilder 
development environment must be shutdown and restarted to clear this 
condition.  Use of these keywords is on a per variable basis.  i.e.

PrivateWrite integer ii_accesscount
ProtectedRead string is_username


Tabpage.visible
---------------
If you have a window with a tab control with tab pages, and go into 
the script painter for the window, Paste Object shows tabpage_1, 
tabpage_2, etc.  However, if you paste in tabpage_1 and put 
tabpage_1.visible =TRUE, it won't compile.


Using PBSYT050.DLL under Windows 95 - POWERBUILDER ENTERPRISE ONLY
-----------------------------------
In order to use PBSYT050.DLL (Sybase DBLIB interface )under 
Windows95, you must update your OpenClient software with 
EBF # 6282 from Sybase.


Cross-hatching in 3D graphs
---------------------------
3D Pie Chart DataWindow when printed prints the same cross-hatch 
style for the different categories and is not distinguishable.   On 
printed page, two different categories print in the same crosshatch;
although each slice of the pie is printed in a different pattern.  
There's no way to tell which slice of the pie belongs to which 
category.


Find Next Button in Function Painter
------------------------------------
Function Painter - Find Next Toolbar item does not work.  If you have 
the "Find" dialog up, and hit the "Find Next" button, it works, but if 
you close the dialog and hit the "Find Next" toolbar icon, nothing 
happens.


DB/2 Primary Index Problem - POWERBUILDER ENTERPRISE ONLY
--------------------------
On a Windows for Workgroups client attached to DB2/MVS through PBIBM, 
exporting the syntax of a (primary) index to the log file crashes 
PowerBuilder with a non-specific Application Error.  In the error 
message, there is some garbled text. 

In the Database Painter with a table opened, click on a primary key 
and then select menu option \Object\Export to Log.  You should see 
the error message at this point.


DataWindow Error Event & DataWindow Property Expression
-------------------------------------------------------
The Error event for a DataWindow does not fire when DW property 
expression in the right side of an assignment specifies an invalid 
property. The following statement should trigger the Error event 
because "Borderx" is invalid, but it does not: 

ls_border = dw_1.object.employee_salary.Borderx

During execution, this statement bypasses the Error event script and 
generates this message:

"Cannot convert dwobject in Any variable to string at line xx...."


Select Tables with Long filenames
---------------------------------
'Select Tables' dialog doesn't support horizontal scrollbar for long 
table names.


Changing page order of tab pages
--------------------------------
The order of the inherited pages can not be changed because page 
order is determined by creation order.  Only the added pages can be 
changed. If you change the page order on a descendent window's tab 
control, the change will not be saved.  If you change the page order 
on the ancestor, that change is saved.


Function calls in CHOOSE CASE Statements
----------------------------------------

Cannot call a function dynamically as part of a CHOOSE CASE statement.
The workaround is to assign the function call into a variable and then 
do choose case using that variable.


Cyclical References to User Objects
-----------------------------------
You will GPF if you try to import a User Object if that User Object
references another object that references the original User Object.  
For example: application has two User Objects.  The first, UO_1,
calls a function that is defined in the second User Object, UO_2.  
UO_2's function is passed as an argument an instance of UO_1.  

UO_1 can be exported.  But when attempting to import it, you will
receive a GPF.


Horizontal scrolling for DropDownPictureListBoxes on 16-bit 
-----------------------------------------------------------
DropDownPictureListBoxes don't support hscroll.
 
The option is there, but nothing happens when you choose hscrollbar on 
a DropDownPictureListBox.

16-bit windows does not support CB_SETHORIZONTALEXTENT  which is 
required for proper operation of the horizontal scroll bar.  Because 
this is available for 32-bit, this was not removed.


Update Clause in Dynamic Call
-----------------------------
A dynamic call of update method will not compile.

If you code the following in the Script Painter, it will not compile:

PowerObject l_Po
// This won't compile: Incompatible property Update 
// for type powerobject
l_Po.Dynamic Update()
// This compiles fine
l_Po.Dynamic ResetUpdate()

This is because UPDATE is also a SQL keyword.  If you use the function 
syntax for a function which is also a keyword (as update) you cannot 
make dynamic calls or post. This is a general issue for external calls 
as well as for attempting dynamic calls on an ancestor (as above).  
The workaround is to write a wrapper function which itself does the 
post of update.  
Note:  This does not break any old code; it is a deficiency in using 
the new syntax.


32-bit Watcom C++ Class Builder on Win95
----------------------------------------
For the 32-bit Watcom C++ Class Builder to run correctly under 
Windows 95, you must add the following environment variables to your 
autoexec.bat file.  This example uses short file names, please modify 
"Pwrs" to "Program Files\Powersoft" if you have installed under long 
file names.
SET EDPATH=c:\Pwrs\WatcNT\EDDAT
SET INCLUDE=c:\Pwrs\WatcNT\H;c:\Pwrs\WatcNT\H\NT;
              c:\Pwrs\WatcNT\H\SYS;%INCLUDE%
SET WATCOM=c:\Pwrs\WatcNT


FOR FURTHER INFORMATION
-----------------------
  1.  Powersoft offers an electronic Bulletin Board Service
to all users of Powersoft Enterprise Series products. This
BBS enables you to upload PowerBuilder libraries for review
by technical support engineers.  It also enables you to
download fixes for released software, code samples,
documentation, the latest training course schedules, and
PowerNotes (a series of technical articles).  You can access
the BBS 24 hours a day, 7 days a week, without a fee.

* Powersoft BBS phone number:  USA: (508) 287-1850
                               UK:  +44 1628 597 311
* Connect information:  8 DataBits, No Parity, 1 Stop Bit,
and speeds of up to 28.8 KBPS are supported.

  2.  Powersoft FaxLine documents provide information in the
form of code samples, tips, techniques, and other
documentation sent to your fax machine.  You can use FaxLine
24 hours a day, 7 days a week, without a fee.

*  Powersoft FaxLine phone number:  USA: (508) 287-1600                     
                                    UK: (+44) 1628 597 312

  3.  If you are a CompuServe subscriber, you can use the
Powersoft forum, which is dedicated to answering questions
about products, services, and technical issues.  To access
this forum on CompuServe, type:  

     GO POWERSOFT at any ! prompt. 

  4.  More information can also be found on the Powersoft
Web site:  

     http://www.powersoft.com


********************************************************************
© 1991-1996 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 the express prior written consent of 
Sybase, Inc. and its subsidiaries.
