Connection Information

To perform the requested action, WordPress needs to access your web server. Please enter your FTP credentials to proceed. If you do not remember your credentials, you should contact your web host.

Connection Type

Database connections – PB Docs 105 – PowerBuilder Library

Database connections – PB Docs 105

  2. Powerbuilder Documentation
  3. Powerbuilder Documentation Older
  4. Powerbuilder Documentation 10.5
  5. Database connections – PB Docs 105

Database connections

If you are deploying an executable or component that accesses
a database, your users need access to the DBMS and to the database
your application uses.

note.gif Where to install database connectivity files You do not need to deploy database connectivity
files with a client application that relies on a middle-tier
component on another computer to perform database transactions.
Database connectivity files must be deployed on the computer that
interacts with the database server.

You need to:

  • If necessary,
    install the DBMS runtime (client) files in the application directory
    or in a directory on the system path
    If your application uses a standalone SQL Anywhere
    database, you can install the SQL Anywhere
    Runtime Edition files on the user’s computer. For more
    information, see “SQL Anywhere
    files”    . Otherwise follow the instructions
    and licensing rules specified by the vendor.
  • Make sure each user has access to the database the
    application uses
    If your application uses a local database, install the database
    and any associated files, such as a log file, on the user’s
    computer.

    If your application uses a server database, make sure the
    user’s computer is set up to access the database. This
    may be the task of a database administrator.

  • Install any database interfaces your application
    uses on the user’s computer
  • If your application uses the ODBC interface, configure
    the ODBC database drivers and data sources, as described in “Configuring ODBC data
    sources and drivers”

For more information about database drivers and interfaces,
see:

Native database drivers

Table 41-5 lists
the native database drivers supplied with PowerBuilder. If an application
or component uses the database specified, the file is required on
the computer. The first two characters of the native database file
name are PB, the next three characters identify the database, and
the last two identify the version of PowerBuilder.

Table 41-5: PowerBuilder native database
drivers
Name Required for
PBIN9105.DLL INFORMIX I-Net 9
PBO84105.DLL Oracle 8.0.x and Oracle8i 8.1.x
PBO90105.DLL Oracle9i
PBO10105.DLL Oracle 10g
PBDIR105.DLL Sybase DirectConnect
PBASE105.DLL Sybase Adaptive Server Enterprise CT-LIB
for Adaptive Server 15 only
PBSYC105.DLL Sybase Adaptive Server Enterprise CT-LIB
PBSYJ105.DLL Sybase Adaptive Server Enterprise CT-LIB
for EAServer deployment only

Installed path Program FilesSybaseSharedPowerBuilder

Deployment path Same directory as the application, in a directory on the system
path, or in the App Path registry key.

Registry entries See “App Path registry key”.

Notes When you deploy a PowerBuilder custom class user object to EAServer, you need to use the SYJ
database interface rather than SYC to connect to an Adaptive Server
Enterprise database. You cannot use SYJ in the PowerBuilder development
environment, but you can use the SYJ Database Profile Setup dialog
box to set the appropriate connection parameters. You can then copy
the syntax from the Preview tab into the script for your Transaction object.

ODBC database drivers and supporting files

This section lists files that are required for all ODBC database
connections from PowerBuilder or InfoMaker applications, as well
as files required for a specific database interface or DBMS.

PowerBuilder ODBC interface files

The following PowerBuilder ODBC interface files are required
if your application uses ODBC:

Table 41-6: PowerBuilder ODBC interface files
Name Description
PBODB105.DLL PowerBuilder ODBC interface
PBODB105.INI PowerBuilder ODBC initialization file

Installed path Program FilesSybaseSharedPowerBuilder

Deployment path Same directory as the application, in a directory on the system
path, or in the App Path registry key.

Registry entries See “App Path registry key”.

Notes The INI and DLL files must be in the same directory. If you
have modified the PBODB105 initialization file,
make sure you deploy the modified version.

Microsoft ODBC files

Table 41-7 lists
the Microsoft ODBC files that are required if your application uses
ODBC.

Table 41-7: Microsoft ODBC files
Name Description
DS16GT.DLL
DS32GT.DLL
ODBC32.DLL
ODBC32GT.DLL
ODBCAD32.EXE
ODBCCP32.CPL
ODBCCP32.DLL
ODBCCR32.DLL
ODBCINST.CNT
ODBCINST.HLP
ODBCINT.DLL
ODBCTRAC.DLL		 Microsoft ODBC driver manager, DLLs,
and Help files

Installed path Windows system directory.

Deployment path Windows system directory.

Registry entries None.

Notes The Microsoft ODBC Driver Manager (ODBC32.DLL)
and supporting files are usually already installed in the user’s
Windows system directory. You can use the redistributable MDAC_TYP.EXE setup
file in the Support directory on the CD to
update users’ systems if necessary.

PB DataDirect ODBC drivers and supporting files

The PB DataDirect ODBC files in Table 41-8 are required if you use the database
interface specified. For each database interface, the table shows required
registry entries. In the string values, replace %SHARED% with
the path to the directory where the drivers are installed.

note.gif Optional Help files Help files need only be deployed if you expect users to perform
database administration tasks. The help files are in HTML format
and are installed in the Help subdirectory
of the DataDirect directory. The names of the
Help files for each driver begin with the letter R and include the
name of the database interface. For example, the files for Adaptive
Server are named Rase.html, Rase2.html,
and so forth.

Table 41-8: PowerBuilder DataDirect ODBC
files
Name Driver and registry entry:
IVPB.LIC
PBICU22.dll
PBTRN22.dll 		All PB DataDirect OEM 5.20 drivers. Registry
entry:
PBBTR22.DLL
PBBTR22R.DLL
PBBTR22S.DLL 		PB DataDirect OEM 5.20 Btrieve. Registry
entry:
PBDB222.DLL
PBDB222R.DLL		 PB DataDirect OEM 5.20 DB2 Wire Protocol.
Registry entry:

PBDBF22.DLL
PBDBF22R.DLL 		PB DataDirect OEM 5.20 dBASE. Registry
entry:
PBIFCL22.DLL
PBIFCL22R.DLL 		PB DataDirect OEM 5.20 Informix Wire
Protocol. Registry entry:
PBORA22.DLL
PBORA22R.DLL 		PB DataDirect OEM 5.20 Oracle Wire Protocol.
Registry entry:
PBIDP22.DLL
PBIDP22R.DLL
PBIDP22S.DLL 		PB DataDirect OEM 5.20 Paradox. Registry
entry:
PBMSSS22.DLL
PBMSSS22R.DLL 		PB DataDirect OEM 5.20 SQL Server Wire
Protocol. Registry entry:
PBASE22.DLL
PBASE22R.DLL		 PB DataDirect OEM 5.20 Sybase Adaptive
Server Enterprise Wire Protocol. Registry entry:
PBTXT22.DLL
PBTXT22R.DLL 		PB DataDirect OEM 5.20 Text File. Registry
entry:
PBXML22.DLL
PBXML22R.DLL
PBXML22S.DLL
PBIADX09.DLL
PBIADX09R.DLL
PBXMLX09.DLL
PBXMLX09R.DLL		 PB DataDirect OEM 5.20 XML. Registry
entry:

Installed path Program FilesSybaseSharedDataDirect52

Deployment path Same directory as the application, in a directory on the system
path, or in the App Path registry key.

Registry entries See table, and also “App Path registry key” and “Configuring ODBC data
sources and drivers” on page .

SQL Anywhere
files

If your PowerBuilder application uses a SQL Anywhere
database, you need to deploy the SQL Anywhere
DBMS as well as SQL Anywhere’s
ODBC database drivers.

note.gif Restrictions PowerBuilder includes SQL Anywhere
for use during the development process. However, this product cannot
be deployed royalty-free to your users.

If your application requires the data definition language
(DDL), a transaction log, stored procedures, or triggers, see your
Sybase sales representative.

For more information about deploying SQL Anywhere
databases and applications, see the SQL Anywhere
documentation.

If your application uses a standalone database, you can deploy
the SQL Anywhere Desktop Runtime
System to users’ computers without incurring additional
license fees. The runtime system allows the user to retrieve and modify
data in the database, but does not allow modifications to the database schema.
It does not support transaction logs, stored procedures, or triggers.

Table 41-9 lists
some of the files that are included in the SQL Anywhere Desktop
Runtime System installation. For more information see the RuntimeEdition.html
file
in the installed directory.

Table 41-9: SQL Anywhere
files
Name Description
dbodbc10.dll SQL Anywhere
ODBC driver
dbbackup.exe SQL Anywhere
backup utility
dbcon10.dll Connection dialog box, required if you
do not provide your own dialog box and your end users are to create their
own data sources, if they need to enter user IDs and passwords when
connecting to the database, or if they need to display the Connection
dialog box for any other purpose
dbisqlc.exe Interactive SQL utility
dblgen10.dll Language-specific string library (EN indicates
the English version)
dblib10.dll Interface library
dbtool10.dll SQL Anywhere
database tools
dbunlspt.exe SQL Anywhere
unload utility
dbvalid.exe SQL Anywhere
validation utility
rteng10.exe Restricted runtime engine
dbctrs10.dll Performance utility
dbserv10.dll Server utility

Installed path Program FilesSybaseSQL
Anywhere 10win32

Deployment path Same directory as the application, in a directory on the system
path, or in the App Path registry key.

Registry entries See “App Path registry key” and “Configuring ODBC data
sources and drivers”.

Notes Supporting files should be installed in the same directory
as dbodbc10.dll. If you are not using the English
string library, make sure you deploy the appropriate version of
the language-specific string library.

Configuring ODBC data
sources and drivers

ODBC.INI To allow the user to connect to a particular data source,
your installation program must provide a definition for that data
source in the ODBC.INI key in the registry on the computer that
accesses the data source, in HKEY_CURRENT_USER for
a user DSN or in HKEY_LOCAL_MACHINE for a
system DSN. The data source definition specifies the name and location
of the database driver as well as the command required to start
the database engine. The data source in the ODBC Data Sources key
must also be listed in ODBC.INI.

The following shows typical registry entries for a data source
called MyApp DB that uses SQL Anywhere.
Registry keys are enclosed in square brackets and are followed by
string values for that key in the format “Name“=”Value“:

ODBCINST.INI Your installation program needs to make two types of entry
in the ODBCINST.INI key in HKEY_LOCAL_MACHINESOFTWAREODBC for
each driver that your deployed application uses:

  • Add
    a string value with the name of the driver and the data value “Installed”
    to the ODBC DRIVERS key in ODBCINST.INI
  • Add a new key for each driver to the ODBCINST.INI key
    with string values for Driver and Setup
    Some drivers require additional string values in ODBCINST.INI.

If the ODBC database driver files are not located in a directory
on the system path, you also need to add their location to the App
Paths key for the executable file.

If you are using ODBC drivers obtained from a vendor, you
can use the driver’s setup program to install the driver
and create registry entries.

The following shows typical registry entries for SQL Anywhere. A registry key is enclosed
in square brackets and is followed by string values for the key
in the format “Name“=”Value“:

For more information about the contents of
the registry entries for ODBC drivers and data sources, see Connecting
to Your Database
.

OLE DB database providers

If your application uses OLE DB to access data, you must install
Microsoft’s Data Access Components software on each user’s
computer if it is not installed already.

You can use the MDAC_TYP.EXE setup
file in the Support directory on the CD to
update users’ computers. The Microsoft OLE DB providers, SQLOLEDB and MSDASQL, are installed when you run MDAC_TYP.EXE.

The files listed in Table 41-10 are required if you use the PB DataDirect
OLE DB data provider specified. If your application uses an OLE
DB data provider from another vendor, you must still deploy PBOLE105.DLL as
well as the files specified by the vendor.

note.gif Optional Help files Help (.HLP and .CNT)
files need only be deployed if you expect users to perform database
administration tasks.

Table 41-10: PowerBuilder DataDirect OLE DB
files
Name Required for
PBOLE105.DLL PowerBuilder OLE DB interface required
for all OLE DB connections
401COMUPD.EXE
IVODBC.LIC
PBADMIN.CNT
PBADMIN.EXE
PBADMIN.HLP
PBADMINR.DLL
PBIAC09.CNT
PBIAC09.DLL
PBIAC09.HLP
PBIAC09R.DLL
PBIAD09.DLL
PBIAC09R.DLL
PBIAG09.DLL
PBIAG09R.DLL 		License and help files and administration
utilities required for all PB DataDirect OEM 2.70 OLE DB data providers
PBINF09.CNT
PBINF09.DLL
PBINF09.HLP
PBINF09R.DLL 		PB DataDirect OEM 2.70 Informix9.x
PBOR809.CNT
PBOR809.DLL
PBOR809.HLP
PBOR809R.DLL 		PB DataDirect OEM 2.70 Oracle 8
PBSYB09.CNT
PBSYB09.DLL
PBSYB09.HLP
PBSYB09R.DLL 		PB DataDirect OEM 2.70 Sybase Adaptive
Server Enterprise
PBXML09.CNT
PBXML09.DLL
PBXML09.HLP
PBXML09R.DLL 		PB DataDirect OEM 2.70 XML

Installed path Program FilesSybaseSharedDataDirectOLEDB

Deployment path Same directory as the application, in a directory on the system
path, or in the App Path registry key.

Registry entries Register PBADMINR.DLL, PBINF90R.DLL, PBOR890R.DLL, PBSYB09R.DLL,
and PBXML09R.DLL as shared DLLs. See also“App Path registry key”.

ADO.NET database interface

The PowerBuilder ADO.NET interface supports the OLE DB, Microsoft SQL Server .NET, Oracle ODP.NET,
and Sybase ASE data providers. If you use ADO.NET, you must deploy PBADO105.DLL, Sybase.PowerBuilder.Db.dll, Sybase.PowerBuilder.DbExt.dll,
and, for OLE DB, the OLE DB data provider.

The file PBADO105.DLL is a standard DLL
file, and you can deploy it in the same way as other PowerBuilder
DLLs. However, Sybase.PowerBuilder.Db.dll and Sybase.PowerBuilder.DbExt.dll are
.NET assemblies. You can use one of three techniques to deploy the
files:

  • Deploy Sybase.PowerBuilder.Db.dll and Sybase.PowerBuilder.DbExt.dll in
    the same directory as the executable file that calls the ADO.NET
    driver.
  • Use a .NET application configuration file to assign
    the path of Sybase.PowerBuilder.Db.dll and Sybase.PowerBuilder.DbExt.dll.
    The file contains configuration settings that the common language
    runtime (CLR) reads as well as settings that the application reads.
    For an executable file, the configuration file has the same name
    as the executable file with the extension .config.
    The pb105.exe.config file in your PowerBuilder
    10.5 directory is an example.
    For more information about configuration files, see the Microsoft
    Visual Studio SDK documentation.
  • Add the Sybase.PowerBuilder.Db.dll and Sybase.PowerBuilder.DbExt.dll assemblies
    to the Global Assembly Cache (GAC). Use this technique only when
    an assembly must be shared by several applications. You can no longer
    install an application using xcopy if one of
    the assemblies it uses is in the GAC.
    For more information about the GAC, see the section on the
    Global Assembly Cache in the Microsoft Visual Studio SDK documentation.

JDBC database interface

The PowerBuilder JDB interface supports the Sun Java Runtime
Environment (JRE) versions 1.2 and later.

If your application or component uses JDBC connections, you
must deploy the JDB driver as well as the appropriate Java package
for the Java VM you are using. The Java virtual machine and a vendor-supplied
JDBC-compliant driver, such as Sybase jConnect® for JDBC,
must also be installed and configured on the computer that accesses
the data source.

For more information about the Java VM, see “Java support”.

Table 41-11: PowerBuilder JDB files
Name Description
PBJDB105.DLL PowerBuilder JDBC Driver (JDB) for JRE
1.2 or later
pbjdbc12105.jar Java package for PowerBuilder JDB driver
and JRE 1.2 or later

Installed path Program FilesSybaseSharedPowerBuilder

Deployment path Same directory as the application, in a directory on the system
path, or in the App Path registry key.

Registry entries Make sure the CLASSPATH environment variable includes the
PowerBuilder pbjdbc12105.jar file. For example:

Notes See “PowerBuilder components
on EAServer “ and “Web DataWindow on EAServer “.

Document get from Powerbuilder help
Thank you for watching.
Powerbuilder Documentation 10.5
PB Docs 105 Powerbuilder Application Techniques Powerbuilder Documentation Powerbuilder Documentation 10.5 Powerbuilder Documentation Older
August 3, 2023
Was this article helpful?
4
5
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x