Using BDE-enabled Datasets

Go Up to Using BDE-enabled datasets Index

Attention: The Borland Database Engine (BDE) has been deprecated, so it will not be enhanced. For instance, BDE will never have Unicode support. You should not undertake new development with BDE. Consider migrating your existing database applications from BDE to dbExpress.

BDE-enabled datasets use the Borland Database Engine (BDE) to access data. They inherit the common dataset capabilities described in Understanding Datasets - Overview, using the BDE to provide the implementation. In addition, all BDE datasets add properties, events, and methods for:

• Associating a Dataset with Database and Session Connections.
• Caching BLOBs.
• Obtaining a BDE handle.

There are three BDE-enabled datasets:

• TTable, a table type dataset that represents all of the rows and columns of a single database table. See Using TTable for a description of features unique to TTable.
• TQuery, a query-type dataset that encapsulates a SQL statement and enables applications to access the resulting records, if any. See Using TQuery for a description of features unique to TQuery.
• TStoredProc, a stored procedure-type dataset that executes a stored procedure that is defined on a database server. See Using TStoredProc for a description of features unique to TStoredProc.

Note: In addition to the three types of BDE-enabled datasets, there is a BDE-based client dataset (TBDEClientDataSet) that can be used for caching updates.

See Also

• Connecting to Databases with TDatabase
• Managing Database Sessions Using TSession