RAD Studio for Microsoft .NET - Embarcadero Technologies

1.1 Developing Database Applications with RAD Studio for Microsoft .NET AdoDbx Client Overview
Deploying Database Applications for the .NET Framework ( see page 24) When deploying database applications using RAD Studio, copy the necessary
runtime assemblies and driver DLLs for deployment to a specified location. The
following sections list the name of the assemblies and DLLs and the location of
where each should reside.
Note: We strongly encourage you to use ADO.NET and the AdoDbx Client
Provider for .NET database applications. The Borland Data Provider is being
deprecated.
Data Providers for Microsoft .NET ( see page 27) In addition to supporting the providers included in the .NET Framework, RAD
Studio includes AdoDbxClient Providers for Microsoft .NET.AdoDbx Client is an
implementation of the .NET Provider and connects to a number of popular
databases.
This topic includes:
• Data Provider Architecture
• AdoDbx Client Advantages
• AdoDbx Client and ADO.NET Components
• Supported AdoDbx Client Providers
• AdoDbx Client Data Types
• AdoDbx Client Interfaces
Stored Procedure Overview ( see page 29) All relational databases have certain features in common that allow applications
to store and manipulate data. A stored procedure is a self-contained program
written in a language specific to the database system. A stored procedure
typically handles frequently repeated database-related tasks, and is especially
useful for operations that act on large numbers of records or that use aggregate
or mathematical functions. Stored procedures are typically stored on the
database server.
Calling a stored procedure is similar to invoking a SQL command, and RAD
Studio provides support for using stored procedures in much the same ways as it
supports editing and... more ( see page 29)
dbExpress Framework ( see page 30) The dbExpress framework (DBX framework) is a set of abstract classes provided
in the unit DBXCommon. Applications can interface with the framework in several
ways: using the framework directly for both native and managed applications,
and using the dbExpress VCL components that are layered on top of the
framework for both native and managed applications.
Although many applications interface with dbExpress drivers via the dbExpress
VCL components, the DBX framework offers a convenient, lighter weight option
to communicate with a database driver. You can also create a database driver for
dbExpress by extending the frameworks's DBXCommon abstract base classes.
The... more ( see page 30)
dbExpress Framework Compatibility ( see page 31) Some dbExpress software developed prior to the dbExpress driver framework
(DBX driver framework) has been modified to work with the DBX driver
framework. As a result of these changes, some compatibility issues arise.
Getting Started with InterBase Express ( see page 32) InterBase Express (IBX) is a set of data access components that provide a
means of accessing data from InterBase databases. The InterBase
Administration Components, which require InterBase 6, are described after the
InterBase data access components.
1.1.1 AdoDbx Client Overview
The AdoDbx Client implements an ADO.NET 2.0 provider for all dbExpress version 4 drivers that implement the newer extended
metadata added to dbExpress 4. All dbExpress drivers shipped with Delphi implement the newer extended metadata.
AdoDbx Client is an implementation of the ADO.NET 2.0 Provider classes. ADO.NET Provider is a set of classes that provide
database services for .NET. It provides access to relational databases, XML and application data. You can use it to develop front
end database applications as well as multi-tier business applications.
See .NET Framework Developer's Guide ADO.NET in the Microsoft documentation for more information.
Here are the key classes in the AdoDbx Client ADO.NET implementation.
• TAdoDbxCommand. Represents a SQL statement or stored procedure to execute against a data source.
5
1