Borland Database Engine
|This article does not cite any sources. (September 2015)|
Borland’s Turbo Pascal had a "database" Toolbox add-on, it was the beginning of the Borland compiler add-ons that facilitated database connectivity. Then came the Paradox Engine for Windows – PXENGWIN – which could be compiled into a program to facilitate connectivity to Paradox tables.
The first DLL-based connectivity engine was ODAPI (Open Database API). It represented Borland’s attempt to centralise connectivity in its suite of applications which included the brand-new Paradox for Windows 4 and Quattro. With version 4.5 / 5.0 of Paradox for Windows, this database engine was crystallised as IDAPI.
In 2000, Borland introduced a new SQL driver architecture called dbExpress, which deprecated BDE SQL links technology.
In 2014, Embarcadero removed the BDE installer from its Rad Studio XE7 install, making it a separate download in order to strengthen the message that the BDE has been deprecated for a number of years. Programmers using the BDE are encouraged to update their software to use newer database connectivity technologies like Embarcadero's FireDAC, or third party provided solutions.
The included set of database drivers enables consistent access to standard data sources: Paradox, dBASE, FoxPro, Access, and text databases. You can add Microsoft ODBC drivers as needed to the built-in ODBC socket. Optionally, Borland's SQL Links product provides access to a range of database management systems (DBMS), including Informix, DB2, InterBase, Oracle, and Sybase.
BDE is object-oriented in design. At runtime, application developers interact with BDE by creating various BDE objects. These runtime objects are then used to manipulate database entities, such as tables and queries. BDE's application program interface (API) provides direct C and C++ optimized access to the database engine, as well as BDE's built-in drivers for dBASE, Paradox, FoxPro, Access, and text databases.
BDE system is configured using the BDE Administrator (BDEADMIN.EXE).
Included with BDE is Borland's Local SQL, a subset of ANSI-92 SQL enhanced to support Paradox and dBASE (standard) naming conventions for tables and fields (called "columns" in SQL). Local SQL lets you use SQL to query "local" standard database tables that do not reside on a database server as well as "remote" DBMS servers. Local SQL is also essential to make multi-table queries across both local standard tables and those on remote SQL servers.
The older name for the BDE API is the "Integrated Database Application Program Interface" or "IDAPI".