BDE组件套TQuery\TTable\TStoreProce结束历时使命。
ADO组件套也停止更新，
将来是FireDAC组件套的江湖
Migrating BDE Applications to FireDAC
Go Up to Migrating to FireDAC
This article guides you through a series of the steps to migrate the BDE application to the FireDAC.
Topics
| Topic | Description |
|---|---|
| BDE Name Counterparts | Most of the BDE high-level types and components have counterparts in FireDAC. |
| BDE Aliases Migration | FireDAC has the BDE aliases migration function. |
| BDE Application Migration | A step-by-step example showing how to migrate BDE application to FireDAC. |
| Additional Migration Hints | Few additional BDE application migration considerations. |
Introduction
This article provides a tutorial showing how to migrate a simple client-server application using BDE data access components, such as TDatabase, TQuery, TTable, to the FireDAC. It shows the basic principles of replacing the common components, properties and code, preserving the developers working time and avoiding the common migration pitfalls.
Overview
In general, the FireDAC components have a high compatibility level with the BDE data access components. This includes the syntax and semantic of the properties and methods in the FireDAC and BDE. But some parts are different:
- BDE and FireDAC have components with different names (for example, TQuery component in BDE is TFDQuery in FireDAC.)
- BDE and FireDAC have different alias/connection definition systems. BDE stores aliases in the binary system wide file IDAPI.CFG, while FireDAC stores the connection definitions in the FDConnectionDefs.ini file.
- Some parameters for BDE SQLLink and FireDAC drivers are different.
- BDE and FireDAC can have different data type mapping for the same RDBMS. FireDAC follows a mapping style closely similar to the dbExpress data type mapping. However, FireDAC has powerful capabilities to adjust the data type mapping.
- The base APIs (the BDE API and the Phys interface) are absolutely incompatible. If you have some code which directly uses the BDE API, it has to be recoded.
- BDE and FireDAC have different query syntax and capabilities. FireDAC offers the Local SQL feature.
This is nearly all that needs to be changed at the migration from BDE to FireDAC. After the migration (or in parallel with it), you should consider reviewing your application for:
- Using the extended FireDAC functionality to simplify your application.
- Using the extended FireDAC functionality to extend the functionality of your application.
- Using the FireDAC options to fine-tune your application and speed it up.
以前安装控件需要bdertl,xe7里移出
工程里不能包含DBTables文件了
#include <dbtables.hpp>
[ilink32 Error] Fatal: Unable to open file 'BDERTL.LIB'
bdertl.lib 工程文件移出OK
[bcc32 Error] DBTables.hpp(11): E2209 Unable to open include file 'Bde.DBTables.hpp'
find #include <dbtables.hpp> in the project,and remove it.ok!
Berlin 版BDE升级FireDAC的工具
http://community.embarcadero.com/blogs?view=entry&id=8594
需要BDE控件的话，可以安装
1）30522_bde_installer_for_rad_studio_delphi_c_builder_10.1_berlin 2016-04-21
BDEInstall.exe
2)Add Package
IDE/Component/Install Packages/Add、dclbdexxx.bpl
D:\Program Files (x86)\Embarcadero\Studio\19.0\bin
http://support.embarcadero.com/article/44082
tokyo 10.2.2 BDE安装
https://cc.embarcadero.com/item/30752