ADO.Net VCL for Delphi (ADONetVCL) is the fastest and most reliable database connectivity solutions for any database using ADO.Net technology in Delphi. It provides data access to data sources such as SQL Server, Oracle, SQLite and to data sources exposed through OLE DB and ODBC using ADO.Net data provider framework. ADONetVCL is an enterprise solution with highest performance and unlimited possibilities. Data-sharing consumer applications can use ADONetVCL to connect to these data sources and retrieve, handle, and update the data that they contain.
With its powerful common architecture base on ADO.Net technology, ADONetVCL enables high-speed direct data access from Delphi to SQL Server, Oracle, SQLite and other data sources exposed through OLE DB and ODBC. ADONetVCL provides a library of components for connecting to a database, executing commands, and retrieving results. Those results are either processed directly, placed in a Virtual Table components. You have the choice of either using client-side or server-side cursors. The ADONetVCL actually handle the work of cursors. The developer has the freedom of choice in development, for creating efficient applications.
The ADONetVCL consists of the following library of Data Access components:
SqlClientDAC is a feature-rich and high-performance library of components that provides native connectivity to SQL Server from Delphi for both 32-bit and 64-bit Windows platforms. SqlClientDAC-based applications connect to SQL Server directly through the ADO.Net SqlClient, which is a .NET Framework Data Provider for SQL Server. SqlClientDAC aims to assist programmers in developing of fast and native SQL Server database applications. SqlClientDAC uses its own protocol to communicate with SQL Server and it is lightweight and performs well because it is optimized to access a SQL Server directly without adding an OLE DB or Open Database Connectivity (ODBC) layer.
OracleClientDAC is a feature-rich and high-performance library of components that provides native connectivity to Oracle from Delphi for both 32-bit and 64-bit Windows platforms. OracleClientDAC-based applications connect to Oracle directly through the ADO.Net OracleClient, which is an Oracle Data Provider for .NET (ODP.Net). OracleClientDAC aims to assist programmers in developing of fast and native Oracle database applications. OracleClientDAC allows developers to take advantage of advanced Oracle database functionality, including Real Application Clusters, self-tuning statement cache, and fast connection failover.
SQLiteDAC is a feature-rich and high-performance library of components that provides native connectivity to SQLite from Delphi for both 32-bit and 64-bit Windows platforms. SQLiteDAC-based DB applications are easy to deploy, do not require installation of other data provider layers (such as BDE or ODBC), and that's why they can work faster than the ones based on standard Delphi data connectivity solutions. SQLiteDAC-based applications connect to SQLite directly through the SQLite.Net, which is an ADO.NET provider for SQLite.
ODBCDAC is a feature-rich and high-performance library of components that provides data access for data sources exposed through ODBC from Delphi for both 32-bit and 64-bit Windows platforms. ODBCDAC-based applications connects to any data source exposed through ODBC using the .NET Framework Data Provider for ODBC. ODBCDAC aims to assist programmers in developing of fast and native database applications. ODBCDAC uses the native ODBC Driver Manager (DM) to enable data access.
ODBCDAC requires the x86 or x64 ODBC driver to be installed according to ODBC specification. Please see the following ODBC documentation:
OLEDBDAC is a feature-rich and high-performance library of components that provides data access for data sources exposed through OLE DB from Delphi for both 32-bit and 64-bit Windows platforms. OLEDBDAC aims to assist programmers in developing of fast and native database applications. OLEDBDAC uses native OLE DB through COM interop to enable data access. OLEDBDAC does not support OLE DB version 2.5 interfaces. OLE DB Providers that require support for OLE DB 2.5 interfaces will not function correctly with the OLE DB Data Access Components. This includes the Microsoft OLE DB provider for Exchange and the Microsoft OLE DB provider for Internet Publishing.
OLEDBDAC does not work with the OLE DB provider for ODBC (MSDASQL). To access an ODBC data source, use the ODBC Data Access Components.
Virtual Table Components is a feature-rich and high-performance library of components that provides an in-memory cache of data retrieved from a data source. It offers a disconnected data source architecture which means there is no need of active connections during work with this component. It can be used to hold multiple tables with data. You can select data form tables, create views based on table. The component also provides you with rich features like saving data as XML and loading XML data.
Note: Direct Data Access components for the following data sources will be available in future: MySQL, Firebird, BD2, Informix etc. However, you can still connect to these data sources using ODBC Data Access Components or OLE DB Data Access Components provided ODBC drivers or OLE DB providers are installed on the client machine.
▪Direct access to server data without using client library. Does not require installation of other data provider layers (such as BDE).
▪Interface compatible with standard data access methods, such as ADO.
▪Bulk copying of data from a data source to Sql server database using TSqlClientBulkCopy component.
▪Supports the posting of deferred updates, so called Cached Updates.
▪Provides methods to sort the records. The dataset sorting allows you to get the required records order without requiring a database.
▪Provides methods to filter the records. The dataset filtering allows you to get record subsets based on a condition.
▪Provides flexible support for master-detail relationships between datasets.
▪Support prefetching rows - specifies the number of rows that are to be fetched per server round trip. This is controlled by FetchOptions.RowsetSize property.
▪Easy to deploy
✓Network and connectivity
▪Disconnected mode with automatic connection control for working with data offline.
▪Transmission is via XML format, therefore can pass through firewalls.
▪Full support of the latest server versions
▪Compatible with Code Gear RAD Studio 2009, Embarcadero RAD Studio 2010, XE, XE2, XE3, XE4, XE5, XE6, XE7, XE8, Seattle, Berlin, Tokyo.
▪Support for all standard and third-party visual data-aware controls.
▪High performance access to the data source.
▪Fast controlled fetch of large data blocks.
▪Advanced connection pooling.
▪High performance of applying cached updates with batches controlled by UpdateOptions.UpdateBatchSize property.
▪Fast locate in a sorted datasets.
▪High performance batch processing.
▪Intelligent fetch block size control.
▪Rowset fetching support using TDbRecordSet Class which mimics the behaviour of ADO RecordSet Object using ADO.Net technology.
▪ADO.NET Data Access components uses XML to store and transfer data among applications, which provide fast access of data for desktop and distributed applications.
✓Local data storage operations
▪CachedUpdates operation mode controlled UpdateOptions.UpdateMode property.
▪Local sorting and filtering, including by calculated and lookup fields.
▪Local master/detail relationship.
✓Data access and data management automation
▪Automatic data updating with Query, Table, and StoredProc components.
▪Fast-forward data retrieval with DataReader component.
▪Automatic record refreshing and locking.
▪Automatic query preparing.
▪Data export and import to/from XML.
▪ADONet VCL for Delphi Home Page - http://crystalnet-tech.com/ADONetVcl/ADODotNet