RAD Studio for Microsoft .NET |  |

Developing Database Applications with ADO.NET
Collapse All

ADO.NET presents a coherent programming model for exposing data access within the .NET Framework. In addition to supporting MS SQL, Oracle, and OLE DB connection components within the .NET Framework, RAD Studio includes data providers for .NET (AdoDbxClient Provider). AdoDbx supports access to MS SQL, Oracle, DB2, and Interbase. AdoDbx component designers ease the generation and configuration of AdoDbx components.

If you are developing new VCL Forms applications for the .NET Framework, or you are migrating existing Win32 VCL Forms applications to the .NET Framework, RAD Studio provides continued support for existing Delphi database technologies, such as dbExpress and dbGo.

This section includes conceptual information about how to use RAD Studio with the ADO.NET architecture, as well as the VCL for .NET database technologies. and how to build a simple ADO.NET project.

Topics

Name | Description
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... more
VCL for .NET Database Technologies | In most cases, the AdoDbxClient Provider provides the best database connectivity solution for your .NET applications. However, if you are developing new VCL Forms applications for the .NET Framework, or you are migrating existing Win32 VCL Forms applications to the .NET Framework, RAD Studio provides continued support for existing Delphi database technologies. RAD Studio provides a migration path from Delphi database technologies running strictly on Win32 clients to the .NET Framework. In addition to being able to build new database applications using ADO.NET, you can migrate existing database applications to take advantage of .NET capabilities. The Delphi database technologies now... more
AdoDbx.NET Data Types | AdoDbx Client data types map to .NET logical types. Dependant upon the database, AdoDbx Client data types map to native data types. Where applicable, AdoDbx Client provides: Consistent data type mapping across databases. Logical data types mapped to .NET native types.
ADO.NET Overview | ADO.NET is the .NET programming environment for building database applications based on native database formats or XML data. ADO.NET is designed as a back-end data store for all Microsoft .NET programming models, including Web Forms and Web Services. Use ADO.NET to manage data in the .NET Framework. Note: BDP.NET is based on ADO.NET 1.1. AdoDbx Client is based on .NET 2.0. CodeGear provides tools to simplify rapid ADO.NET development using AdoDbx Client and Borland Data Providers for .NET (BDP.NET). If you are familiar with rapid application development (RAD) and object oriented programming (OOP) using properties, methods, and events, you will... more
BDP Migration Overview | BDP (Borland Data Provider) is being deprecated, and you should not use BDP for new development. Instead, you should use AdoDbx Client. This topic describes differences and equivalencies between BDP and AdoDbx Client. As a result of the deprecation of BDP: BDP will be removed from the product in a future release. There will be no further BDP development and minimal QA effort. Only critical bugs will be fixed. No additional documentation will be provided, though documentation is not yet removed. BDP was based on ADO.NET 1.1. Many of the differentiating features of BDP, such as provider independence and extended... more
Blackfish SQL Overview | The design and implementation of Blackfish SQL emphasizes database performance, scalability, ease of use, and a strong adherence to industry standards. Blackfish SQL capabilities include the following: Industry standards compliance Entry level SQL-92 Unicode storage of character data Unicode-based collation key support for sorting and indexing dbExpress 4 drivers for win32 Delphi and C++ ADO.NET 2.0 providers for .NET JDBC for Java JavaBean data access components for Java XA/JTA Distributed transactions for Java High performance and scalability for demanding online transaction processing (OLTP) and decision support system (DSS) applications Delphi, C#, and VB.NET stored procedures and triggers for Windows Java-stored... more
ADO.NET Component Designers | Almost all distributed applications revolve around reading and updating information in databases. Different applications you develop using ADO.NET have different requirements for working with data. For instance, you might develop a simple application that displays data on a form. Or, you might develop an application that provides a way to share data information with another company. In any case, you need to have an understanding of certain fundamental concepts about the data approach in ADO.NET. Using these designers, you can work efficiently to access, expose, and edit data through database server-specific schema objects like tables, views, and indexes. These designers... more
Deploying Database Applications for the .NET Framework | 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 | 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 | 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
dbExpress Framework | 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
dbExpress Framework Compatibility | 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 | 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.

Copyright(C) 2008 CodeGear(TM). All Rights Reserved.
What do you think about this topic? Send feedback!