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.

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

The following table 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.


Required for






Oracle 10g


Oracle 11g


SQL Native Client for Microsoft SQL Server




Adaptive Server Enterprise CT-LIB for Adaptive Server 15 only


Adaptive Server Enterprise CT-LIB

Installed path


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.

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:




PowerBuilder ODBC interface


PowerBuilder ODBC initialization file

Installed path


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.


The PBODB190.ini file must be in a directory defined by the HKEY_CURRENT_USER\Software\sybase\PowerBuilder\19.0\InitPath registry setting or, in the absence of that key,  in the same directory as the DLL file. In most cases, the target deployment machine will not have the registry setting and, therefore, the INI file should be in the same directory as the DLL.

Microsoft ODBC files

The following table lists the Microsoft ODBC files that are required if your application uses ODBC.















Microsoft ODBC driver manager, DLLs, and Help files

Installed path

Windows system directory.

Deployment path

Windows system directory.

Registry entries



The Microsoft ODBC Driver Manager (ODBC32.dll) and supporting files are usually already installed in the user's Windows system directory.

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.


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  sales representative.

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.

A full installation for the SQL Anywhere driver, runtime engine, and supporting files is available in the PowerBuilder setup program. 

The following table lists some of the files that are installed. For more information see the RuntimeEdition.html file in the installed SQL Anywhere directory. It contains a list of all the SQL Anywhere files that can be freely deployed with PowerBuilder applications to end users' computers.




SQL Anywhere ODBC driver


SQL Anywhere backup utility


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


Interactive SQL utility


Language-specific string library (EN indicates the English version)


Interface library


SQL Anywhere database tools


SQL Anywhere unload utility


SQL Anywhere validation utility


Restricted runtime engine


License file for restricted runtime engine


Performance utility


Server utility

Installed path

\Program Files\SQL Anywhere 16\bin32 or \bin64

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.

Privilege requirements on Windows 7

When running under User Account Control, the SQL Anywhere restricted runtime engine (rteng11.exe) and other SQL Anywhere executables require elevated privileges. For Windows 7 and later versions of Windows, you can use the SQL Anywhere elevated operations agent (dbelevate11.exe) to elevate the privileges of users running these executables and allow non-elevated client processes to autostart elevated servers or database engines. The following DLLs also require elevated privileges when they are registered and unregistered: dbcon11.dll, dbctrs11.dll, dbodbc11.dll, dboledb11.dll, and dboledba11.dll.


Supporting files should be installed in the same directory as dbodbc11.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


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":

"Driver"="C:\Program Files\SQL Anywhere 16\bin32\dbodbc16.dll"
"Start"="c:\program files\SQL Anywhere 16\bin32\dbeng16.exe -c9m"
"Description"="Database for my application"
"DatabaseFile"="C:\Program Files\myapps\myapp.db"

"MyApp DB"="SQL Anywhere 16.0"


Your installation program needs to make two types of entry in the ODBCINST.INI key in HKEY_LOCAL_MACHINE\SOFTWARE\ODBC 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 a typical registry entry 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":

"Driver"="c:\program files\SQL Anywhere 16\bin32\dbodbc16.dll"
"Setup"="c:\program files\SQL Anywhere 16\bin32\dbodbc16.dll"

For more information about the contents of the registry entries for ODBC drivers and data sources, see the section called “How PowerBuilder accesses the data source” in 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.

The PowerBuilder OLE DB interface requires the functionality of the Microsoft Data Access Components (MDAC) version 2.8 or later software.

To check the version of MDAC on a computer, users can download and run the MDAC Component Checker utility from the MDAC Downloads page at

On the Windows 7/8.1/10 operating systems, the Windows Data Access Components (DAC) version 6.0 replaces MDAC, and implements the functionality requirements of the PowerBuilder OLE DB interface.

OLE DB data providers

Several Microsoft OLE DB data providers are automatically installed with MDAC and DAC, including the providers for SQL Server (SQLOLEDB) and ODBC (MSDASQL).

PowerBuilder OLE DB interface files

The PowerBuilder OLE DB interface file is required if your application uses OLE DB. The ODBC initialization file is required if you have used it to customize OLE DB settings:




PowerBuilder OLE DB interface


PowerBuilder ODBC initialization file

Installed path


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.


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

ADO.NET database interface

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

The files pbado190.dll and pbrth190.dll are standard DLL files, and you can deploy them 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 pb190.exe.config file in your PowerBuilder 2019 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). For more information about the GAC, see the section on the Global Assembly Cache in the Microsoft Visual Studio SDK documentation. If you use the Runtime Packager, the assemblies are installed in the GAC.

JDBC database interface

The PowerBuilder JDB interface supports the Java Runtime Environment (JRE) versions 1.6 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 SAP 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.




PowerBuilder JDBC Driver (JDB) for JRE 1.6 or later


Java package for PowerBuilder JDB driver and JRE 1.6 or later

Installed path


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 pbjdbc12190.jar file. For example:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment]
"CLASSPATH"="C:\Program Files\Appeon\shared\PowerBuilder\pbjdbc12190.jar;...