When you install InfoMaker, shared files that are used by both PowerBuilder and InfoMaker are installed in the Shared\PowerBuilder directory. You need to deploy a subset of these files with your application.
The following tables indicate which feature each file is required to support. For example, PBVM190.dll, PBSHR190.dll, LIBJCC.DLL, and LIBJUTILS.DLL are required for all deployed applications, pbpdf190.dll is required only when your application allows to save reports as PDF files using the NativePDF! method. You need not install some other files unless your application uses the features indicated. You should install the runtime files in the same directory as the application or in a directory on the system path.
Database connections
The runtime files needed to enable database connections are listed separately in Making the data source available.
Core runtime files
The following table lists the core InfoMaker runtime files.
Name |
Required for |
---|---|
pbvm190.dll |
All |
pbshr190.dll |
All. pbvm190.dll has dependencies on this file. |
libjcc.dll |
All. pbvm190.dll has dependencies on this file. |
libsybunic.dll |
All. pbvm190.dll has dependencies on this file. |
libjutils.dll |
All. libjcc.dll has dependencies on this file. |
libjtml.dll |
All. libjcc.dll has dependencies on this file. |
nlwnsck.dll |
All. libjcc.dll has dependencies on this file. |
pbuis190.dll |
All. pbvm190.dll has dependencies on this file. |
pbdwe190.dll |
Reports and forms |
pbresource190.dll |
InfoMaker resource file |
Microsoft files
When you deploy the core InfoMaker runtime files, you must also deploy the msvcr100.dll and msvcp100.dll Microsoft Visual C++ runtime libraries and the Microsoft .NET Active Template Library (ATL) module atl100.dll, if they are not present on the user's computer. The InfoMaker runtime files have a runtime dependency on these files.
Additional runtime files
The following table lists additional runtime files that your application might not require. For example, pbvm190.dll is required for all deployed applications, but pbrtc190.dll and its associated runtime files are required only if your application uses RichText objects.
Name |
Required for |
---|---|
pbdpl190.dll |
Data pipeline support |
PBDWExcel12Interop190.dll, Sybase.PowerBuilder.DataWindow.Excel12.dll |
Excel 2007 support |
pbjvm190.dll |
Java support |
pbrtc190.dll, PBTCTEXT190.dll, TER25.dll, WRS9.dll, spell32.dll, PDC32.dll, WRW9.dll, HTS20.DLL, ssts.dll, SSGP.dll, TXML2.dll |
Rich text support (with TE Edit Control) |
pbrtc190.dll, PBTXTEXT190.dll, tp4ole15.ocx, tp15.dll, tp15_bmp.flt, tp15_css.dll, tp15_doc.dll, tp15_dox.dll, tp15_gif.flt, tp15_htm.dll, tp15_ic.dll, tp15_ic.ini, tp15_jpg.flt, tp15_obj.dll, tp15_pdf.dll, tp15_png.flt, tp15_rtf.dll, tp15_tif.flt, tp15_tls.dll, tp15_wmf.flt, tp15_wnd.dll |
Rich text support with the OEM version of TX Text Control |
PBXerces190.dll, xerces-c_2_8.dll, xerces-depdom_2_8.dll |
XML Web report support and XML support for reports |
pbtra190.dll, pbtrs190.dll |
Database connection tracing |
pbpdf190.dll |
Saving reports as PDF files using the NativePDF! method |
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 InfoMaker.
The localized runtime files let you deploy InfoMaker applications with standard runtime dialog boxes in the local language. They handle language-specific data when the application runs, including:
-
DayName function manipulation
The DayName function returns a name in the language of the runtime files available on the machine where the application is run.
-
DateTime manipulation
When you use the String function to format a date and the month is displayed as text (for example, the display format includes "mmm"), the month is in the language of the runtime files available when the application is run.
-
Error messages
InfoMaker error messages are translated into the language of the runtime files.