|
|
|
...PFC 7 Release Notes:
PB 7.0.2
| PB 7.0.1
| PFC 7.0 + PB 7.0
...PFC 6 Release Notes: PFC 6.5.1 +
PFC 6.5.1 Y2K + PB 6.5.1 | PFC 6.5 + PB 6.5
| PFC 6.0 + PB 6.0
...PFC 5 Release Notes: PFC 5.0.04 +
PFC
5.0.04 Y2K + PB 5.0.04 EBF#3 (includes Y2K fixes) + PB 5.0.04
...PFC 5 Release Notes: PFC 5.0.03 + PB 5.0.03 | PFC 5.0.02 | PFC
5.0.01
...PFC/PB Release Downloads: Maintenance Downloads
...PFC Upgrade Check List: Cheat Sheet Upgrade
Check List | PFCGuide
Migration Check List | Faxback #44505
...PFC/PB
Y2K FAQ
PFC/PB Y2K FAQ] PB 5.0.04 EBF#3 (includes Y2K fixes) (Below)] PB 5.0.04
EBF#4 (also includes Y2K fixes) (But it is not included here)]PowerBuilder Foundation Class Library Version 5.0.04
RELEASE NOTES
*****************************************************************
* *
* Welcome to PFC Version 5.0.04 for PowerBuilder. *
* *
*****************************************************************
Copyright Ê 1996-1997 Sybase, Inc. and its subsidiaries. All rights
reserved.
Updated 2/12/98
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 Extension Objects
Changes and Bugs Fixed
Documentation Updates
Miscellaneous
=================================================================
NEW EXTENSION OBJECTS
=================================================================
There are no new extension objects for version 5.0.04.
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 #44505.
Note: this step is only necessary for migrating existing PFC
applications to a newer version of PFC.
5.0.02 n_cst_platformmac pfeapsrv.pbl
5.0.02 n_cst_filesrvmac pfeapsrv.pbl
5.0.02 n_cst_platformsol2 pfeapsrv.pbl
5.0.02 n_cst_filesrvsol2 pfeapsrv.pbl
5.0.02 w_print pfeapsrv.pbl
=================================================================
CHANGES AND BUGS FIXED
=================================================================
Platform Service
----------------
Object: pfc_n_cst_platformwin32
Method:
Fix: Fixed local external function header declaration to use only
long type variables.
Tech support#: 423587, 431396
Object: pfc_n_cst_platformwin32, pfc_n_cst_platformsol2
Method: of_FindWindow()
Fix: Set local external call classname parameter to null. You can
now also find non PowerBuilder windows.
Tech support#:
File Service
------------
Object: pfc_n_cst_filesrv
Method: of_SortDirList(...)
Fix: Corrected so that local datastore is destroyed.
Tech support#:
Object: pfc_n_cst_filesrv
Method: of_GetAllFilesSpecifier
Fix: Made protected instance variable value available via public
function.
Tech support#:
Object: pfc_n_cst_filesrv
Method: of_FileWrite(...)
Fix: Corrected to handle writing of strings > 60k.
Tech support#: 489023
Object: pfc_n_cst_filesrvwin32
Method:
Fix: Fixed local external function header declaration to use only
long type variables.
Tech support#: 423587, 431396
Object: pfc_n_cst_filesrvwin32, pfc_n_cst_filesrvsol2,
pfc_n_cst_filesrvmac
Method: of_ConvertPBDatetimeToFile(...)
Fix: Corrected milisecond formatting which caused overflow of millisecond uint.
Tech support#: 423591
Date Service
------------
Object: pfc_n_cst_datetime
Method: of_IsValid(date)
Fix: Corrected so that the valid date 1-1-1900 stops returning
INVALID. Previously, 1-1-1900 was being returned as an
invalid date but in reality it is a valid date.
***************************************************************
** Please note that the function will now return a valid for **
** 1-1-1900. **
***************************************************************
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
Error Message Service
---------------------
Object: pfc_n_cst_error
Method: of_Message(...)
Fix: Corrected ll_rowcount datatype from integer to long.
Tech support#: 409402
Object: pfc_n_cst_error
Method: of_Message(...)
Fix: Removed beep(1) call that was not needed.
Tech support#: 490782
Object: pfc_w_message
Method:
Fix: Corrected slight truncation of bitmaps.
Tech support#: 385842
Object: pfc_w_message
Method: open
Fix: Corrected so that correct tab order is encountered. Default
button is set.
Tech support#: 490843
DataWindow Caching Service
--------------------------
Object: pfc_n_cst_dwcache
Method: of_Refresh(...)
Fix: Corrected arguments that were erroneously being passed twice to
the Retrieve operation.
Tech support#: 404567
Application Manager
-------------------
Object: pfc_n_cst_appmanager
Method: of_IsRegistryAvailable(...)
Fix: Corrected so that (OSType=Windows! and OSMajorRevision=3 and
OSMinorRevision >= 95) does not return TRUE. A 16bit
application cannot access the registry.
Tech support#: 331536
Conversion Service
------------------
Object: pfc_n_cst_conversion
Method: of_Date(...)
Fix: Enhanced to handle more conversion cases.
Tech support#: 466242
Object: pfc_n_cst_conversion
Method: of_Time(...)
Fix: Enhanced to handle more conversion cases.
Tech support#: 466242
DataWindow/DataStore Base Service
---------------------------------
Object: pfc_n_cst_dwsrv, pfc_n_cst_dssrv
Method: of_GetItem(...)
Fix: Corrected case where number, decimal and real value were being converted
into a long.
Corrected so that LookUpDisplay values for DropDownListBoxes
are handled.
Corrected so that computed fields expressions are properly
evaluated.
Tech support#: 456405, 432602, 468405
Object: pfc_n_cst_dwsrv, pfc_n_cst_dssrv
Method: of_GetItem(...)
Fix: Corrected case where number, decimal and real value were being
converted into a long.
Tech support#: 456405, 432602
Object: pfc_n_cst_dwsrv, pfc_n_cst_dssrv
Method: of_DWArguments(...)
Fix: Corrected so that the loop to get multiple arguments works in
all cases.
Tech support#: 400784
DataWindow Linkage Service
--------------------------
Object: pfc_n_cst_dwsrv_linkage
Method: pfc_insertrow(...)
Fix: Ensure that detail datawindows linked through dwShareData get
synchronized.
Tech support#: 389299
Object: pfc_n_cst_dwsrv_linkage
Method: of_SetArguments(...)
Fix: Enhanced to validate columns prior to registering them.
Tech support#: 420783
Object: pfc_n_cst_dwsrv_linkage
Method: of_Retrieve(...)
Fix: Corrected so (when appropriate) scrolling occurs to the
desired row.
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 Sort Service
-----------------------
Object: pfc_n_cst_dwsrv_sort
Method: pfc_sortdlg
Fix: Corrected so that focus is returned to the requestor
datawindow.
Tech support#: 490765
DataWindow Filter Service
-----------------------
Object: pfc_n_cst_dwsrv_filter
Method: pfc_filterdlg
Fix: Corrected so that focus is returned to the requestor
datawindow.
Tech support#: 490765
DataWindow PrintPreview Service
-------------------------------
Object: pfc_n_cst_dwsrv_printpreview
Method: of_SetEnabled(...)
Fix: Corrected by adding check to prevent error condition when
datawindow is nested.
Tech support#: 401957
DataWindow Row Manager Service
------------------------------
Object: pfc_n_cst_dwsrv_rowmanager
Method: of_DeleteSelected(...)
Fix: Allow for non-PFC code to select the current row in the
rowfocuschanged event.
Tech support#: 461006
Object: pfc_n_cst_dwsrv_rowmanager
Method: of_DeleteAll(...)
Fix: Corrected so that return code is the actual number of rows
deleted.
Tech support#: 490897
Status Bar Service
---------------
Object: pfc_n_cst_winsrv_statusbar
Method: of_CalculateMicroHelpHeight(...)
Fix: Updated calculation for a better windows NT 3.x positioning.
Tech support#: 379595
Rich Text Edit
--------------
Object: pfc_u_rte
Method: destructor
Fix: Corrected cleanup for the fileserv. Prior to fix it was
possible for PFC to attempt a destroy on an uninstantiated
reference.
Tech support#: 416076
Tab
---
Object: pfc_u_tab
Method: destructor
Fix: Added cleanup process to object.
Tech support#:
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 the Cut and Copy on the PopUp menu now
work with protect expression.
Tech support#: 498701
DataStore
---------
Object: pfc_n_ds
Method: of_SetBase(...)
Fix: Function now returns 0 if no action was taken.
Tech support#: 490768
ListView
--------
Object: pfc_u_lv
Method: of_CreateKey(...)
Fix: Added code to place a delimiter between concatenated key
values.
Tech support#: 469420
Object: pfc_u_lv
Method: of_SetAttributes(...)
Fix: Corrected the assignment of the overlaypictureindex property.
Tech support#:
Object: pfc_u_lv
Method:
Fix: Corrected PFC code to set the DataStore's transaction via
of_SetTransObject().
Tech support#: 426567
Object: pfc_u_lv
Method: of_DeleteColumns(...)
Fix: Added checks to see if there are columns to delete.
Tech support#:
TreeView
--------
Object: pfc_u_tv
Method: of_FindItem(...), of_SearchChild(...), of_FindFirstItem(...)
Fix: Rewrote functions to be non-recursive. Recursive logic was
causing GPF's on trees with large number of items.
Tech support#: 411618
Object: pfc_u_tv
Method: of_SetItemAttributes
Fix: Corrected the assignment of the overlaypictureindex property.
Tech support#: 411861
Object: pfc_u_tv
Method: of_RefreshItem(...)
Fix: Corrected so that return code returns 1 on success, not 0.
Tech support#: 377319
Object: pfc_u_tv
Method: of_BuildTree(...)
Fix: Made label text the size of the field displaying it in the
dataobject.
Tech support#:
Object: pfc_u_tv
Method: of_CreateKey(...)
Fix: Added code to place a delimiter between concatenated key
values.
Tech support#: 469420
Object: pfc_u_tv
Method:
Fix: Corrected PFC code to set the DataStore's transaction via
of_SetTransObject().
Tech support#: 426567
Object: pfc_u_tv
Method: of_SetDataSource(...)
Fix: Enhanced function to return more meaningful return values.
-4 when label column does not exist. -5 when a transaction
fails.
Tech support#: 426572
Object: pfc_u_tv
Method: of_PopulateLevel(...)
Fix: Enhanced function to return more meaningful return values.
Tech support#: 426572
Menu
----
Object: pfc_m_master
Method: m_window
Fix: Corrected minimize all functionality which left all other
window positioning menu items permanently disabled.
Tech support#: 473367
Window
------
Object: pfc_w_master
Method: CloseQuery
Fix: Corrected so that window for which the message is displayed is
not hidden prior to displaying its closequery message.
Tech support#: 473364
Object: pfc_w_splash, pfc_w_logon, pfc_w_about
Method: Open
Fix: Corrected so that if there is no application logo the
picture control will be made invisible.
Tech support#: 460506
Object: pfc_w_splash
Method: Open
Fix: Enhanced so that the window is centered.
Tech support#: 490841
Debugging
---------
Object: pfc_n_cst_sqlspy, d_debuglog
Method:
Fix: Corrected by adding the century to the date format.
Tech support#: 497810
Security
--------
Object: d_pfcsecurity_controllist, d_pfcsecurity_info_update,
d_pfcsecurity_report_by_user, d_pfcsecurity_report_by_window
Method:
Fix: Removed quotes from where clause for compatibility with
multiple databases.
Tech support#: 366982
Object: d_pfcsecurity_report_bu_user
Method:
Fix: Renamed retrieval argument so that it is not a reserved
word for oracle databases.
Tech support#: 454777
=================================================================
DOCUMENTATION UPDATES
=================================================================
The security scanner utility (found in the pfcsecsc.pbl library)
cannot be run from the PB development environment. It must be
created as a single executable file. The executable must be named
'pfcsecsc.exe' and be located in either the current directory or
in a directory on the path. The security scanner utility is run
by the PFC Security Administration utility (which can be run from
the development environment).
=================================================================
MISSCELLANEOUS
=================================================================
We would like to thank you for your support for PFC.
Your feedback and suggestions for the product are welcome by
sending email to pfc@powersoft.com
PFC Development Team
February 1998
...PFC 7 Release Notes:
PB 7.0.2
| PB 7.0.1
| PFC 7.0 + PB 7.0
...PFC 6 Release Notes: PFC 6.5.1 +
PFC 6.5.1 Y2K + PB 6.5.1 | PFC 6.5 + PB 6.5
| PFC 6.0 + PB 6.0
...PFC 5 Release Notes: PFC 5.0.04 +
PFC
5.0.04 Y2K + PB 5.0.04 EBF#3 (includes Y2K fixes) + PB 5.0.04
...PFC 5 Release Notes: PFC 5.0.03 + PB 5.0.03 | PFC 5.0.02 | PFC
5.0.01
...PFC/PB Release Downloads: Maintenance Downloads
...PFC Upgrade Check List: Cheat Sheet Upgrade
Check List | PFCGuide
Migration Check List | Faxback #44505
...PFC/PB
Y2K FAQ
PB 5.0.04 EBF#3 (includes Y2K fixes) (Below)]PowerBuilder Foundation Class (PFC) Y2K 5.0.04\6.5.1 Fixes
==========================================================
The Y2K patches are delivered as a complete set of PFC libraries (including extensions).
If you are already using PFC you should replace only your main PFC libraries and not your
extension libraries.
For example:
Version 5.0.04:
Replace pfcapsrv.pbl, pfcdwsrv.pbl, pfcmain.pbl, pfcwnsrv.pbl
Version 6.5.1:
Replace pfcapsrv.pbl, pfcdwsrv.pbl, pfcmain.pbl, pfcwnsrv.pbl, pfcutil.pbl
If an attempt to fix these Y2K issues has been made by overriding these PFC functions in
your own customized extension layer, first compare the official fixes with your own
changes. Remove the overriding functions in your customized extension layer only if they
address the fixes included in this set of Y2K patches.
For example: a Y2K issue is addressed by modifiying n_cst_datetime and overriding the
function of_lastdayofmonth. After the patches are applied,
pfc_n_cst_datetime::of_lastdayofmonth now includes these changes, therefore
of_lastdayofmonth in n_cst_datetime should be removed from your customized extension
layer.
After applying the Y2K patches, it is advised to perform a Full Rebuild of the
application.
-----------------------------------------------------------
Object: pfc_n_cst_datetime DateTime Service
CR169790
Method: of_lastdayofmonth
Fix: Removed a loop which relied on an invalid date.
Added an array containing the number of days in each month.
Fix Release: 7.0GA, 6.5.1(y2kpatch), 5.0.04(y2kpatch)
CR162134
Method: of_relativemonth
Fix: Removed a loop which determined the last day in month.
The loop was relying on the of_IsValid(date) function to find an invalid date. In PB
5.0.03+ a date variable can only contain a Null or a valid date.
Fix Release: 7.0GA, 6.5.1(y2kpatch), 5.0.04(y2kpatch)
CR188246
Method: of_relativeyear
Fix: Removed a loop which determined the last day in month.
The loop was relying on the of_IsValid(date) function to find an invalid date. In PB
5.0.03+ a date variable can only contain a Null or a valid date.
Fix Release: 7.0GA, 6.5.1(y2kpatch), 5.0.04(y2kpatch)
=========================================================
Object: pfc_u_calendar Drop Down Calendar
CRs 162134 and 184373
Method: of_drawmonth
Fix: Did not redraw date of 1/1/1900. Removed an invalid comparison to
date(‘50/50/1900’)). The comparison is no longer needed. Post 5.0.03
PowerBuilder date type cannot contain an invalid date with an exception of a null value.
Fix Release: 7.0GA, 6.5.1(y2kpatch), n/a for 5.0
CRs 162134 and 184373
Method: of_setdate
Fix: Add code to always redraw for date matching 1/1/1900 to allow date display for
January 1900. Previously the calendar did not redraw since the initial value of the
previous date was also 1/1/1900.
Fix Release: 7.0GA, 6.5.1(y2kpatch), n/a for 5.0
CRs 162134 and 184373
Method: of_reset
Fix: If the date is invalid set the calendar date to today's date.
Fix Release: 7.0GA, 6.5.1(y2kpatch), n/a for 5.0
...PFC 7 Release Notes:
PB 7.0.2
| PB 7.0.1
| PFC 7.0 + PB 7.0
...PFC 6 Release Notes: PFC 6.5.1 +
PFC 6.5.1 Y2K + PB 6.5.1 | PFC 6.5 + PB 6.5
| PFC 6.0 + PB 6.0
...PFC 5 Release Notes: PFC 5.0.04 +
PFC
5.0.04 Y2K + PB 5.0.04 EBF#3 (includes Y2K fixes) + PB 5.0.04
...PFC 5 Release Notes: PFC 5.0.03 + PB 5.0.03 | PFC 5.0.02 | PFC
5.0.01
...PFC/PB Release Downloads: Maintenance Downloads
...PFC Upgrade Check List: Cheat Sheet Upgrade
Check List | PFCGuide
Migration Check List | Faxback #44505
...PFC/PB
Y2K FAQ
PB 5.0.04 EBF#3 (includes Y2K fixes) (Below)]Release Notes for PowerBuilder[TM] Maintenance Release 5.0.04
(c) 1991-1998 Sybase, Inc. and its subsidiaries. All rights reserved.
Updated 3/18/98 10:25
************************************************************************
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.
For free access to the technical bulletin infobase on the web (updated daily), use the
Folio
Web search engine at:
http://info.sybase.com (main page)
The query URL:
http://info.sybase.com/cgi-bin/folioisa.dll/techbull.nfo/query=?realquerydlg
(Use the "records with hits" checkbox so you only get records that match your
text search).
************************************************************************
Section I: General Information
Section II: Known Issues with PowerBuilder 5.0.04
===============================
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, Windows NT 3.51, Windows 3.x, or higher for development
- Windows 95, Windows NT, or Window 3.x for deployment
Macintosh
- PowerPC, 68030, or 68040 processor for development
- PowerPC, 68030, or 68040 processor for deployment
- 12 MB RAM for PowerPC, or 20 MB RAM for 68K processors
- 45 MB hard drive space, depending on configuration
- CD ROM drive
- Macintosh System 7.6.1 software
Sun Solaris
- Sun Sparc - Sun 4 class computer
- 32 MB RAM
- 100 MB hard drive space
- swap file space - 2 1/2 times the amount of physical memory
- CD ROM drive
- Solaris 2.5.1 (Sun OS 5.5.1)
- CDE 1.01 with DTWM or MWM
- Sun Sparc C++ 4.1 compiler, for compiled code
Database Information
--------------------
SQLAnywhere 5.5.03 is installed for Windows 16, and 32-bit platforms.
Oracle 8 Driver - PowerBuilder 5.0.04 includes a beta version of a driver for Oracle8. We
do
not expect to release this driver in a GA version until 6.0.01, it is included to
facilitate
migration to PowerBuilder 6.0.
Installing on NT4.0
-------------------
You must have Administrator privileges to fully install this product on NT 4.0.
Internet Explorer 4.0
---------------------
We are aware that files installed by the newly released Internet Explorer 4.0 have
introduced
some painting and other issues in PowerBuilder and InfoMaker. We are tracking these
issues,
but will not be able to address them until a future maintenance release.
ODBC Updates
------------
If you download Microsoft's updated ODBC files (ODBC version 3.50.3308) for use with
PowerBuilder or InfoMaker, please be aware that they have not been fully tested with our
products, and results may be unpredictable.
Online Books
------------
Online Books are now available over the Web! The URL for the DynaWeb version of the PB5
and
IM5 online books is: http://calas.sybase.com
.
Companion Products
-------------------
There are some new Companion Products available with this maintenance release:
Updated InstallBuilder
Updated Translation Toolkit
Updated Advanced Developer Toolkit (includes PFC)
Updated localized runtimes
Updated Internet Developer Toolkit (see separate directory on CD for DLLs)
IDT Updated DLLs
-----------------
It is required that you manually update the IDT DLLs when installing the 5.0.04
maintenance.
Depending on your web server configuration you will need to copy the appropriate DLL to
the
required directory. Listed below are the common install directories for the various web
servers, your directory may vary:
Web Server Directory Interface(s)
--------------- ----------------- -----------------------------
O'Reilly Website \website\cgi-shl pbcgi050.exe
Microsoft IIS \inetpub\scripts pbisa050.dll, pbcgi050.exe
Netscape:
Enterprise 3.0 \netscape\suitespot\bin pbns3050.dll, pbcgi050.exe
Ent 2.0/Fasttrack \netscape\bin pbns2050.dll, pbcgi050.exe
FastTrack \netscape\bin pbns2050.dll, pbcgi050.exe
Solaris servers /opt/pb5/pb5web/bin pbcgi050.exe
Included in this release is a new NS-API interface DLL (pbns3050.dll) for the Netscape
Enterprise v3.x web server. The updated IDT DLLs in the \IDT directory on the CD. You
should
save a copy of your old DLLs before updated to the new version.
Also included in the \IDT directory are the latest version of the Window and Datawindow
plugins. The 16-bit version of the plugins are located in the \IDT\Plugin16 directory. The
appropriate DLL(s) need be copied to the Netscape or Internet Explorer plugins directory.
The
filenames for the plugins are:
Window nppba050.dll
DataWindow npdwe050.dll
If you are updating the Window Plugin on a browser client computer, you are also required
to
upgrade the Powerbuilder Deployment Kit (PBDK).
Updated Database Help
---------------------
The following database topics have been updated in the 5.0.04 Help files:
* OR8 Oracle 8.0 database interface (Beta version)
* Using Oracle 8 user-defined types
* Sybase SQL Anywhere Version 5.5.03
* DateTimeAllowed DBParm parameter (for MSS, SYB, SYC, SYD, and SYT)
* ModifySyntax DBParm parameter (for SYC)
* PWDialog DBParm parameter (for SYC and SYD)
* ThreadSafe DBParm parameter (for O73 and OR8)
* Support for DBGetTime in SYT
* Support for AutoCommit in NET
* Final support in PBSYC on Windows 16-bit for Sybase Open Client security and directory
services
* CallEscape DBParm for ODBC (see full description below)
New DBParm: CallEscape
----------------------
Controls whether the Powersoft ODBC interface uses call escape syntax for stored procedure
calls (the default) or converts the calls to driver-specific native SQL syntax before
sending
the command to the ODBC driver.
Applies to ODBC interface (if driver and backend DBMS support this feature)
Syntax: CallEscape = 'value', where value controls whether the ODBC interface uses call
escape
syntax for stored procedure calls or converts the calls to driver-specific native SQL
syntax.
Values are:
* Yes (Default) The ODBC interface uses call escape syntax for stored procedure calls
* No The ODBC interface converts stored procedure calls to driver-specific native SQL
syntax
before sending the command to the ODBC driver.
When to use Set CallEscape
Set to No if the ODBC driver you are using expects to receive stored procedure calls in
native
(driver-specific) SQL syntax instead of in call escape syntax. For information about the
stored
procedure call syntax your ODBC driver expects, see your vendor's driver documentation.
Level 2 or higher ODBC driver required to use the CallEscape DBParm parameter, your ODBC
driver
must meet Level 2 or higher API conformance requirements. CallEscape has no effect when
you are
using an ODBC driver that meets Core or Level 1 API conformance requirements.
Call Escape Syntax Example
The following example shows a call to a stored procedure named sp_test that uses call
escape
syntax: {call sp_test(1,1)}
To convert stored procedure calls to native SQL syntax before sending the command to your
ODBC
driver, set CallEscape to 'No' 'in either of the following ways:
Database profile Type the following in the DBParm box in the Database Profile Setup dialog
box:
CallEscape = 'No'
- or -
PowerBuilder application script Type the following in a PowerBuilder script:
SQLCA.dbParm = "CallEscape = 'No'"
===================================================
Section II: Known Issues with PowerBuilder 5.0.04
===================================================
Note: Issues are on all platforms unless otherwise designated.
InstallBuilder update from 5.0.00 Enterprise only:
The install will not automatically check the update box for Install Builder. You will need
to
click on the checkbox, for Install Builder to install properly, and you will need to
change the
default directory in the install directory box to include "Pb5i32" in the
pathname.
For example, if you installed PB 5.0.00 Enterprise into c:\Pwrs, the default directory for
the
maintenance release will be expecting InstallBuilder to be in c:\Pwrs\InsBld32. Since that
is
*not* where it was installed for PB 5.0.00 Enterprise, the instbldr.exe is not found, and
the
box
is not checked automatically for the updates. For the installation to succeed, check the
box
and change the path to: c:\Pwrs\Pb5i32\InsBld32. If you are updating a 5.0.01, 5.0.02 or
5.0.03 *Enterprise* release with the 5.0.04 Maintenance updates, this is not an issue.
Bug# 49477: Oracle drivers: When creating a datawindow from SQL syntax using unqualified
column
names based on Oracle table aliases, the DW column names consist of "c" followed
by the actual
column name.
Bug# 49104: All Database Interfaces. The routine that parses DBParms does not allow a
numeric
DBParm value to be delimited by a blank space. It must end with a null terminator or a
comma
in order to be processed correctly. This means that a user who mistakenly types
DBParm="UTF8=1 , DBTextLimit=32000 , PacketSize=8096 " will get none of these
parms processed
correctly. Moreover, there is no warning of any sorts to indicate that something was
wrong.
Bug# 49080: Oracle 8.0.03, DBMS=OR8: DataWindow select statements that have a retrieval
argument. Preview data, enter in value for retrieval argument, error displays:
"Unreasonable
or unimplemented conversion requested."
Retrieval of data is successful under these scenarios:
- There is any DBParm (w/out StaticBind, which it will default to 1)
- Set StaticBind = 1 explicitly even though it is considered to be the default
- Set StaticBind = 0 and DisableBind = 1
- Set DisableBind = 1
Bug# 48110: Oracle drivers: Using the old Put_Line function calls for creating Oracle
stored
procedure source DataWindows gives a ORA-6550 error when using dates as input arguments.
This
worked fine in 4.0.
Bug# 47919: Oracle drivers (only going to server version 7.3.3.0). Problem displaying
division
results in SELECT statement when using Oracle Workgroups Server 7.3.3.0.0 The problem
appears
when the number to display is a fraction with more then 37 digits after decimal point.
'Select
1/3 from dual' gives the error.
Bug# 47045: Oracle 8 driver: DataWindow with stored procedure datasource does not work if
SQLCache is set to a positive number.
Bug# 43086: Using Oracle 7.3 driver (PBO73050.DLL) & DBParm=DisableBind=0 (default).
Select
using a host variable other than decimal (long or integer), and its value is greater than
127,
no records are found. Returns is 100.
Bug# 13664: Oracle drivers: with tablecriteria = ' ,,' ('blank comma comma') synonyms are
NOT returned in table list. With tablecriteria= ',,' ('comma comma') synonyms are returned
in table list. According to documentation in Connecting to your Database, for Oracle when
you
specify TableCriteria= ',,'
The names displayed in your select tables list should be for Tables and Views only, no
Synonyms. This does not work.
Bug# 49825:
Page fault occurs in call to PB OLE Automation server when calling functions where:
a) PB is an OLE server and a simple data type is passed by value.
b) PB has an OLE control which fires an event which passes simple types by value.
Bug# 47952
Currency(7) editmask on a numeric column deletes the currency symbol if you type in a '.'
or
',' and after that bad behavior results. Also, if you doubleclick on the value to
highlight the
editmask of type currency and press DELETE nothing happens.
Bug# 49279
SyntaxfromSQL is erratic and inconsistent in how it's working in development and runtime
with
respect to DDDW columns. Most drivers are affected. This also affects PowerDesigner since
the
PB-Gen process uses SyntaxfromSQL() when you use a native driver. The DataWindows
generated
from PowerDesigner in 5.0.04 will not have extended attributes, until this bug is fixed.
Bug# 48837
If a function returns an ANY datatype variable and a NULL decimal variable is cast into
the ANY
return value, the function call GPFs in pfcdwsrv.DLL at the RETURN statement of the
function if
you're using machine code. There are no problems in development or p-code. ALL other
numeric
datatypes work in machine code with NULLs using of_getitemany() - datawindow types ULONG,
LONG,
REAL, NUMBER all work correctly.
Workaround: (for PFC users)
First option
============
Make the calls to Getitemdecimal() manually rather than using of_getitemany(). You could
evaluate the "Describe("#1.coltype") and only if it returns
"decimal", use Getitemdecimal()
manually with in-line script.
Second Option
=============
Object: pfc_n_cst_dwsrv
Function of_getitemany() format 4 - returns ANY
CASE....
...
CASE "decim"
la_value = dw_1.GetItemDecimal ( al_row, as_column, adw_buffer, ab_orig_value )
// Add some checking code here
if isnull(la_value) then
decimal ld
ld = "-100"
la_value = ld
// cast this with a NON-null but identifyable value so it doesn't GPF at the 'return' call
return la_value
/*----------- end of of_getitemany() function ----------*/
/* back in powerscript - trap for your decimal NULL condition*/
decimal ld_decimal
setnull(ld_decimal)
if of_getitemany(x, y) = -100 then
setitem(a,b,ld_decimal)
end if
**********************************************************************
(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 Alexander Klimenko for passing this along to us
...PFC 7 Release Notes:
PB 7.0.2
| PB 7.0.1
| PFC 7.0 + PB 7.0
...PFC 6 Release Notes: PFC 6.5.1 +
PFC 6.5.1 Y2K + PB 6.5.1 | PFC 6.5 + PB 6.5
| PFC 6.0 + PB 6.0
...PFC 5 Release Notes: PFC 5.0.04 +
PFC
5.0.04 Y2K + PB 5.0.04 EBF#3 (includes Y2K fixes) + PB 5.0.04
...PFC 5 Release Notes: PFC 5.0.03 + PB 5.0.03 | PFC 5.0.02 | PFC
5.0.01
...PFC/PB Release Downloads: Maintenance Downloads
...PFC Upgrade Check List: Cheat Sheet Upgrade
Check List | PFCGuide
Migration Check List | Faxback #44505
...PFC/PB
Y2K FAQ
PB 5.0.04 EBF#4 also includes Y2K fixes, but it is not included here)] PowerBuilder 5.0.04 EBF 3 build 78 Released 21-Sep-1999
(c) 1991-1999 Sybase, Inc. and its subsidiaries. All rights reserved.
Updated 09/21/99
*************************************************************************
If you are viewing this file in Wordpad, please use the word-wrap option.
IMPORTANT: For information about changes to PB 5.x support which became effective August
1, 1999 (i.e., Y2K support only), please visit:
http://support.sybase.com/HotTopics/Item/0,1012,47,00.html
Disclaimer
----------
The DLLs included in this zip file represent emergency bug fixes (EBF) for PowerBuilder
version 5.0.04. This EBF build has been system tested with automated test suites, and unit
tested for the specific bugs (see details below under "Change Requests
included"). If you decide to use these DLLs it will be necessary for you to test your
entire application. These isolated fixes are also included in PB 6.5x and PB 7.0x, where
applicable.
To use these DLLs, rename the existing DLLs in the shared and deployment directories, then
add the new DLLs to the same directories.
These DLLs are deployable and supported.
Question: What is meant by "supported"? Answer: If you encounter a Y2K specific
regression (i.e. something that worked previously and is now broken) as a result of using
these DLLs, please report the problem and include the EBF build number that you are using.
When a new EBF build is available that addresses the regression, it will be necessary for
you to replace ALL of your EBF DLLs with the new set of EBF DLLs.
Also, if you are already using any other EBF DLLs, it is a requirement that all EBF DLLs
on your PC must be replaced with DLLs from the same EBF build number. This requirement is
due to the fact that there are links and dependencies between EBF DLLs. If all EBF DLLs on
your PC do not come from the same build number, unexpected/undesirable behavior will
result.
Compatibility
-------------
This EBF should be installed over PB version 5.0.04 GA (build 76). You should shut down
any applications and backup the files in the directories below before copying over the new
files.
Change Requests Included
------------------------
NEW FIXES FOR 5.0.04 EBF3:
-------------------------
Database Fixes:
202979 - "Select error: SQL Error -930 Can not connect to database server
(ts_informix7), has occurred" when you attempt a retrieve as needed datawindow
retrieve using the IN5 or IN7 driver.
Datawindow Fixes:
201595 - DW EditMask incorrectly identifies NULL Values as dates (as either 01/01/2000, or
01/01/1900).
194183 - EditMask 00-00-0000 tab off turns to 01-01-0000.
PREVIOUS/CUMULATIVE FIXES FROM 5.0.04 EBF2:
------------------------------------------
Database Fixes:
164577 - MS SQL Server 6.5 - EXECUTing Stored procedure returns correct value as long as
the output value is an INTEGER. If it is a string or a getdate() being returned the
following error will occur: Error 242 "implicit conversion from datatype varchar to
int is not allowed use the convert function to run this query".
188243 - Database Painter problems using MS SQL 6.5 with service pack 5 for Y2K fixes.
Datawindow Fixes:
165780 - PB Stack fault if using the MS Pen driver and checkbox/radiobutton/editmask.
185319 - Back space or delete key causes cursor to move before and after the decimal point
in an Edit Mask.
186240 - Unable to print a RichText Datawindow using PrintDatawindow(). PrintJob just sits
in the queue.
187161 - Cursor gets stuck in an Edit Mask when using the BackSpace key.
PREVIOUS/CUMULATIVE FIXES FROM 5.0.04 EBF1:
------------------------------------------
Database Fixes:
162365 - Memory leak when you do an iterative call to retrieve() of a datawindow connected
to Informix 7.2 using Inet 5.01.WJ2 client interface and 16-bit PB. NOTE: Created new
16-bit DLL for PB 5.0.04 only called "pbi51050.dll", also requires 5.10WC1
I-Connect.
164820 - When the same column of the same row is being updated by two different instances
of PowerBuilder (Informix IN7 connection) the column being updated by the second instance
is not being updated. The problem is that the user does not receive a message that the row
has changed between retrieve and update.
171269 - On a PowerBuilder SYC connection, connecting takes a long time if the
SYSALTERNATES table contains many entries.
183540 - A pipeline with the commit value set to none, does commits after the updates. The
commit should be under application control.
Datawindow Fixes:
158555 - Datawindow numeric EditMask issue; the cursor goes one position too far after
hitting the decimal point. Not reproducible with US settings. Can use Norwegian, Swedish
or German settings to reproduce, where comma is used as decimal separator.
160504 - Currency(7) editmask on a numeric column deletes the currency symbol if you type
in a '.' or ',' and after that bad behavior results.
164806 - For a DataWindow column of type real / float and a display format with decimal
separator (e.g. #,##0.00) the value displayed is higher than the value typed in.
168496 - CrossstabDialog() generates syntax error when value is replaced in expression.
170685 - Datawindow EditMask mmm-yy cannot work with year 00 (i.e., year 2000).
173766 - The European comma decimal separator disappears if backspace is used in an
editmask. This can only be reproduced with a 'foreign' keyboard layout e.g. German,
French, Spanish etc.
**********************************************************************
(c) 1991-1999 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.
 Home |
|
|
|
|
Home | Top
