Other Changes
\The Sandbox \PB History & Future \New in PB 10 \Other Changes
PD Plug-in
UDDI for
Web Services
Web Services
JSP Deployment to EP
PBNI Changes
DB Connectivity
Misc Changes
Other Changes
XP look and feel
PBNI support 
for Any
for PBNI
for SOAP
Hiding the 
JSP Page view
New options in
SQL Select painters
New Excel format
for saving data
New DBParm:
Additional changes
New in
PB 10.0.1
New in
PB 10.2

EAServer connection caches for Unicode support

The following two new native connection caches have been introduced in EAServer 4.23 with EBF 12014 and EAServer 5.1 with EBF 12015 to support Unicode connection to a database in PowerBuilder 10:

  • OCI_9U – Oracle9i Unicode Cache
  • ODBCU – ODBC Unicode Cache

These connection cache types accept Unicode connection parameters and then send a request to the database driver to open a Unicode connection to the database. With a Unicode connection, PowerBuilder components can communicate with the database using Unicode.

In PowerBuilder 10, if you are using the Oracle9i native interface (O90) to access an Oracle9i database in a PowerBuilder component in EAServer, use the database driver type OCI_9U for the connection cache. If you do not, access will fail.

For an ODBC connection cache, use the database driver type ODBCU to access multiple-language data in an ASA Unicode database or DBCS data in an ASA DBCS database with the database parameter ODBCU_CONLIB set to 1. For example:

    SQLCA.DBParm = "CacheName='EASDemo_u',UseContextObject='Yes',ODBCU_CONLIB=1"

DataDirect 4.2 ODBC drivers

PowerBuilder 10 provides DataDirect 4.2 drivers for ODBC instead of DataDirect 4.1 drivers.

Informix support

PowerBuilder 10 supports the following versions of Informix: 9.0, 9.1, 9.2, and 9.3.

Oracle 10g support

You can use the Oracle9i database interface (pbo90100.dll) with Oracle 10g clients and servers. The following combinations have been tested:






Oracle 10g

Oracle 10g


Oracle 10g

Oracle 10g

Oracle 10g instant client

Oracle 10g

No new Oracle 10g features are supported.

Unicode databases

A Unicode version of the demo database, easdemo10u.db, has been tested and is provided with this release to enable you to perform Unicode testing. The database contains characters from the following languages: English, simplified Chinese, traditional Chinese, Korean, Hebrew, Japanese, French, German, Greek, and Thai.

For international characters to display correctly, you must have them installed on your computer. On Windows 2000, you can install them from the Input Locale page in the Regional Options dialog box in the Windows control panel. On Windows XP, you can install them from the Languages page in the Regional and Languages Options dialog box.

If you plan to test getting multiple language data from a Unicode Adaptive Server database using the SYC or SYJ interface, you must set utf8 to 1 at the end of the database connection parameter. For example:

    DBMS = "SYJ"
    Database = "ase125"
    DBParm ="CacheName='ase125',UseContextObject='Yes',UTF8=1"

PFC available on CodeXchange

The PowerBuilder Professional or PowerBuilder Enterprise setup programs do not include the PowerBuilder Foundation Class library (PFC) as of version 10. A final build of PFC that is compatible with PowerBuilder 10 is available in the PFC.zip file in the Support directory on Disk 1.

PFC is now available on the PowerBuilder CodeXchange Web site for public use and modification. Sybase will make no further enhancements or bug fixes to PFC. The PFC source is in a controlled sub-project on CodeXchange that allows multiple developers to work on the project but provides for a centralized repository with code review.

Web target support

PowerDynamo is not included with EAServer 5.0 and later, and, beginning with PowerBuilder 10, PowerDynamo Web targets are no longer supported. Web targets that do not depend on PowerDynamo are still supported in PowerBuilder 10.

Web DataWindow DTC changes

PowerBuilder 10 allows you to deploy a DataWindow that you select in the Web DataWindow DTC as part of your JSP or Web target. The Generate Path in Script field on the DataWindow page of the Web DataWindow DTC Properties dialog box now contains three radio buttons: Absolute, Relative, and None. By default you generate a Web DataWindow as HTML, but in PowerBuilder 10 you can also generate a Web DataWindow as XML or XHTML.

Exception handling support in machine code

In previous releases of PowerBuilder, you could not use try-catch statements in your code if you planned to distribute your application with machine code DLLs instead of PBDs. This restriction has been removed in PowerBuilder 10.

SaveAsTypes changed

The following file format for saving data has been added: EMF! (Enhanced Metafile). Support for the following formats will be removed in a future release: Excel!, SYLK!, WKS!, WK1!, dBASE2!, and WMF!. WMF graphics should be replaced with EMF graphics. The Excel5! format supports Excel 5, 6, and 7, and Excel8! supports Excel 8 and later versions.

New runtime files

Some functionality, including memory allocation algorithms, has been moved from the pbvm100.dll to pbshr100.dll. When you deploy an application, you must deploy pbshr100.dll with other required PowerBuilder runtime files.

The version of libjcc.dll distributed with PowerBuilder 10.0 has a dependency on a file called libjlog.dll. You must deploy libjlog.dll with other required PowerBuilder runtime files when you deploy applications or components to most deployment targets. Do not deploy either libjcc.dll or libjlog.dll when you deploy to EAServer.

PBL Peeper PB Help PB History
& Future About Us Feedback Site Map

Web www.techno-kitten.com