PowerBuilder runtime files

Database connectivity Files required for database connectivity are listed separately in “Database connections”.

Core runtime files

Table 41-3 lists the core PowerBuilder runtime files.

**Table 41-3: Core PowerBuilder runtime files**
Name	Required for
PBVM105.DLL	All.
PBSHR105.DLL	All. PBVM105.DLL has dependencies on this file.
LIBJCC.DLL	All. PBVM105.DLL has dependencies on this file.
LIBJUTILS.DLL	All. LIBJCC.DLL has dependencies on this file.
PBDWE105.DLL	DataWindows and DataStores.

Microsoft files

When you deploy the core PowerBuilder runtime files, you must also deploy the msvcr71.dll and msvcp71.dll Microsoft Visual C++ runtime libraries if they are not present on the user’s computer. The PowerBuilder runtime files have a runtime dependency on these files.

Microsoft Windows GDI+ is the subsystem of the Windows XP operating system or Windows Server 2003 that implements enhanced graphic capabilities for screens and printers. The PowerBuilder runtime files have a runtime dependency on these files. If you deploy your PowerBuilder application to the Windows 2000 platform, you must make sure that gdiplus.dll is available on the target computer.

The Microsoft .NET Active Template Library (ATL) module, atl71.dll, is included in PowerBuilder 10.5 to support Ink controls. If your application uses Ink controls, you must make sure that the atl71.dll is available on the target computer.

For information about obtaining and redistributing these Microsoft files, see the latest PowerBuilder release bulletin.

Additional runtime files

Table 41-4 lists additional runtime files that your application might not require. For example, PBVM105.DLL is required for all deployed applications, but PBRTC105.DLL and its associated runtime files are required only if your application uses Rich Text controls or RichText DataWindow objects.

For more information about deploying applications that use the PBJVM105.DLL for Java support, see “Java support”.

**Table 41-4: Additional PowerBuilder runtime files**
Name	Required for
PBACC105.DLL	Accessibility support (Section 508)
PBDWR105.DLL, PBDWE105.PBD	Web DataWindow support
PBXerces105.DLL, xerces-c_2_6.dll, xerces-depdom_2_6.dll	XML Web DataWindow support and XML support for DataWindows and DataStores
PBJVM105.DLL	Java support
PBRTC105.DLL, tp11.dll, tp11_bmp.flt, tp11_css.dll, tp11_doc.dll, tp11_gif.flt, tp11_htm.dll, tp11_ic.dll, tp11_ic.ini, tp11_jpg.flt, tp11_obj.dll, tp11_pdf.dll, tp11_png.flt, tp11_rtf.dll, tp11_tif.flt, tp11_tls.dll, tp11_wmf.flt, tp11_wnd.dll, tp4ole11.ocx	Rich Text support
PBLAB105.INI	Label DataWindow presentation-style predefined formats
PBTRA105.DLL, PBTRS105.DLL	Database connection tracing

Installed path \Program Files\Sybase\Shared\PowerBuilder or for most of the required rich text files, \Program Files\Sybase\Shared\PowerBuilder\RTC.

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”.

Localized runtime files

Localized runtime files are provided for French, German, Italian, Spanish, Dutch, Danish, Norwegian, and Swedish. These files are usually available shortly after the general release of a new version of PowerBuilder. The localized runtime files let you deploy PowerBuilder applications with standard runtime dialog boxes in the local language. They handle language-specific data when the application runs.

For more information, see “Localizing the product”.