Summary

Information about the BDE 5.1.1 And 5.2 Merge Modules

Synopsis

• The Borland Database Engine is a data access engine that is used by Delphi, Borland C++ Builder, dBase, and Paradox for Windows. This data access engine consists of the core technology that allows any ODBC driver to be used as an IDAPI driver for any application using the Borland Database Engine. Additionally, the Borland Database Engine can be augmented with optional native SQL drivers that provide transparent and efficient connectivity to widely used SQL servers.
• Borland released a merge module that installs and configures the Borland Database Engine. InstallShield wrapped this merge module to make it easier to use from the IDE. This wrap allows you to install an alias and specify drivers and a destination in the alias. You can use predefined variables like [INSTALLDIR] to specify a path in the alias.
• InstallShield merge module Dependencies: None (ODBC is not required)
• Although BDE merge modules exist for different languages, only one can be installed and used at a time.

Discussion

The Borland Database Engine (BDE) Merge Module will automatically be available if a Borland tool is present on the system when the InstallShield product is installed. Otherwise, the merge module must be obtained from Borland and added to a directory in the Merge Module Locations list. This list can be found by going to the InstallShield menu item Tools->Options and selecting the tab labeled 'Merge Modules'. To learn more about Merge Module Locations, please refer to InstallShield Help Library titled Merge Module Tab.

In order to function properly, the BDE module requires customization. This customization is accomplished with the BDE Designer Wizard. To learn more about the customization steps, please refer to the InstallShield Help Library article titled InstallShield BDE Support.

Version 5.1.1 Released 9/22/00

• The Borland merge module will install BDE 5.1.1 on the target machine.
• If the BDE does not exist on the target machine, the Borland merge module will install the BDE to <PROGRAM FILES>\Common Files\Borland Shared\BDE.
• BDEMERGE.ini must be in the same directory as the MSI package.
• Aliases are not removed during uninstallation. This is by design of the BDE merge module by Borland. An alias should only be removed through the BDE Administrator.
• An existing alias cannot be modified with the merge module. You cannot update or overwrite an existing alias. This is by design of the BDE merge module by Borland to prevent one application from modifying the alias of another application.

Known issue:

The BDE Administrator is not added to the Control Panel. This issue has been reported to Borland.

Additional Information

You can find additional information about the BDE merge module that Borland installed from the readme.txt that is distributed with it. This document contains information about which Borland products the merge module can be used with as well as the difference between the Professional and Enterprise editions of the merge module.

The BDE module is available only if a Borland tool was present on the system when you installed InstallShield 2012 Spring and earlier.

For more information on merge modules, see InstallShield Help Library topics:

• Working with Merge Modules that Are Included in Installation Projects
•  Merge Modules Tab
• Installing BDE Support (InstallShield 2012 Spring and earlier)