Deploying Database Applications
Go Up to Deploying RAD Studio Applications
Applications that access databases involve special installation considerations beyond copying the application's executable file onto the host computer. Database access is most often handled by a separate database engine, whose files cannot be linked into the application's executable file. The data files, when not created beforehand, must be made available to the application. Multi-tier database applications require additional handling on installation, because the files that make up the application are typically located on multiple computers.
Since several different database technologies (ADO, BDE, dbExpress, and InterBase Express) are supported, deployment requirements differ for each. Regardless of which you are using, you need to make sure that the client-side software is installed on the system where you plan to run the database application. ADO, BDE, dbExpress, and InterBase Express also require drivers to interact with the client-side software of the database.
Specific information on how to deploy dbExpress, BDE, and multi-tiered database applications is given in the following topics:
- Deploying dbExpress Database Applications
- Deploying BDE Applications
- Overview of a Three-tiered Application
Database applications that use client datasets such as TClientDataSet or dataset providers require you to include midas.dcu (for Delphi) or midas.hpp (for C++) (for static linking when providing a standalone executable); if you are packaging your application (with the executable and any needed DLLs), you need to include Midas.dll.
- If deploying database applications that use ADO, you need to be sure that MDAC version 2.1 or later is installed on the system where you plan to run the application. MDAC is automatically installed with software such as Windows 2000 and Internet Explorer version 5 or later. You also need to be sure the drivers for the database server you want to connect to are installed on the client. No other deployment steps are required.
- When deploying database applications that use InterBase Express, you need to be sure that the InterBase client is installed on the system where you plan to run the application. InterBase requires gds32.dll and interbase.msg to be located in an accessible directory. No other deployment steps are required. InterBase Express components communicate directly with the InterBase Client API and do not require additional drivers.
- Interbase 2009 is now fully supported, which includes the Interbase To-Go Edition. To-Go is a small, portable version of the RAD Studio Desktop Edition. Target applications for the To-Go edition include small devices and public kiosks, as well as Value Added Reseller (VAR) applications that were built using InterBase. Used in the To-Go edition form, InterBase does not have to be separately installed on any server or end-user workstation. Apart from Interbase 2007 and Interbase 2009, the To-Go edition also supports Interbase SMP 2009. InterBase To-Go requires ibtogo.dll and interbase.msg to be located in an accessible directory.
- If deploying database applications that use MySQL, you need to ensure that MySQL 5.1 is installed on the system where you plan to run the application.
- MS SQL 2008 is now fully supported in RAD Studio Enterprise. All data type mappings are properly supported between dbExpress and MS SQL Server 2008. However, in order to use these data type mappings, you need to install a native SQL client, that is you need to make sure you have a copy of the SQLNCLI10.DLL file. MS SQL Server 2008 Native Client can be downloaded from this link. RAD Studio Enterprise also provides full support for MS SQL Server 2005, in case your operating system does not support the MS SQL 2008 version. In this case, you need to assure you have a copy of the SQLNCLI.DLL file that can be accessed by your application.
- If deploying database applications that use Firebird, you need to install a Firebird client, that is you need to make sure you have a copy of the FBCLIENT.DLL file on the system where you plan to run the application.
- If deploying database applications that use Oracle 11g, install the Oracle Instant Client on the system where you run the application.
In addition to the technologies described here, you can also use third-party database engines to provide database access. Consult the documentation or vendor for the database engine regarding redistribution rights, installation, and configuration.
If the library corresponding to the used technology is not found, an error message is displayed and the application may not run correctly.