BDE exit history migration to 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, suchTdatabase,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 des 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,TqueryComponent In BDE isTfdqueryIn 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 shoshould consider reviewing your application:

• 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.

Category:

• Firedac

BDE exit history migration to firedac