The key to Delphi written in Delphi needs to publish BDE (BDE ", but BDE is large (different versions are different, the latest Delphi5 has 17m), far more than the general program itself . But in fact, some files can not be used, so we can create an installer with Delphi with Delphi, which can streamline our database applications when publishing. Implementation and Application Reference Reference BDE32.HLP "Core BDE Files" under "Introduction to Borland Database Engine", you can know the key files and its roles of BDE, which can be referred to as a basis to streamline the BDE driver. The following is the role of each file: 1. An indispensable file BLW32.dll: Language-driven function library. Idapi32.dll: BDE Basic Library. FareAast.btl, USA.BTL: Far East language and American language drivers are indispensable to Chinese software. IDR20009.DLL: Error Information Library.
Second, the database driver (select one or more as needed) iDasci32.dll: ASCII text database driver log library, if you do not need ASCII text database, you can. IDDAO32.DLL: Access database driver log library, if you don't need Access database, you can. IDDBAS32.DLL: DBase database driver log library, if you don't have a dbase database, you can. IDODBC32.DLL: ODBC Database Driver Release Library, if you don't have to use an ODBC database, don't. IDPDX32.dll: Paradox Database Driver Release Library, if you don't have to use the Paradox database, you can.
Third, other drivers and configuration files (select one or more) iDbat32.dll: Batch Operation Driver Library, if you do not need the TBATCHMOVE control or DbibatchMove class function, you don't. IDDR32.DLL: Data Repository driver function library, if you don't have to use a Data Repository function, you can. IDPROV32.DLL: BDE DataSet Provider driver log library, if you don't have to use a TPROVIDER control, you can. IDQbe32.dll: QBE driver function library, if you don't have query by example, you can. IDSQL32.DLL: SQL query driver log library, if you don't have to query with TQuery, don't. IDapi32.cfg: BDE configuration file, if there is no special requirements in the program, don't. It is also possible to set it correctly after the BDE manager.
Fourth, other documents (generally not) other * .btl: language drivers in other countries and regions, don't. BDE32.HLP, BDE32.cnt: BDE Help file, you can. BDEADMIN.EXE, BDEADMIN.HLP, BDEADMIN.CNT: BDE Manager, and help files, if you don't need software users to configure BDE yourself, you may not. DataBump.exe, DataBump.hlp, DataBump.cnt: Database Data Transfer Tool and Help File, you can. Localsql.hlp, localsql.cnt: SQL query statement help file, don't. SQLLNK32.HLP, SQLLNK32.cnt: SQL Connection Help file, you can. After selecting the file as needed, you should write a registry file. It can be manually set, but it is best to set in the program. If you need to set the registry key value (required to have the correct key value before calling the database operation, each correspondence key value is in the Win9X / NT / WIN2000): Data) The setting of the directory where the driver is located: HKEY_LOCAL_MACHINE / SOFTWARE / BORLAND / DATABASE Engine / DLLPATH (String Value) Language Driver Set: HKEY_LOCAL_MACHINE / SOFTWARE / BORLAND / BLW32 / BLAPIPATH (String Value) Language Driver File Name: HKEY_LOCAL_MACHINE / SOFTWARE / BORLAND / BLW32 / LOCALE_LIB # (string value) where # is numbered, in order is 0, 1, 2, 3 ... such as HKEY_LOCAL_MACHINE / SOFTWARE / BORLAND / BLW32 / LOCALE_LIB0 = "FareAST .btl "HKEY_LOCAL_MACHINE / SOFTWARE / BORLAND /BLW32/LOCALE_LIB1="usa.btl" is enough, you can effectively reduce the size of the BDE driver, such as using the TTable control to operate the Paradox database, as long as IDAPI32 .dll, blw32.dll, idr20009.dll, frareast.btl, usa.btl, idpdx32.dll six files. These files can be placed in any directory, as long as the registry is indicated. BDE is reduced by 17.4m to 1.48m, and only a few hundred k, which makes the program decrease.
