Two classes in this namespace provide data remoting and have not been deprecated, so they do not require migration:

• DataHub
• DataSync

Most BDP classes in this namespace are implementations of ADO.NET classes. These classes are also implemented in AdoDbx Client. Most source code using these classes should convert to AdoDbx Client with little effort. 

The following table shows the correspondence between classes in ADO.NET, BDP and AdoDbx Client:  

Correspondence between classes in ADO.NET, BDP and AdoDbx Client  

Conversion of BDP classes in this group is fairly straightforward. Check the documentation to see if the method you've used is supported in the corresponding AdoDbx Client class. If it is, you probably don't need to do anything. If the method is not supported, then you need to modify your code to use methods that are supported in either AdoDbx Client or ADO.NET itself. 

For example, the class BdpDataReader accesses database records. Most of its data access methods have corresponding TAdoDbxDataReader methods, as described in the ISQLCursor section. BdpDataReader.GetSchemaTable can be used to retrieve cursor metadata as a DataTable. See the ISQLExtendedMetaData and ISQLMetaData section for a description of metadata access for AdoDbx Client.

The BdpCopyTable class does not have a corresponding class in AdoDbx Client, so this capability is not available in AdoDbx Client.

This namespace has seven classes and three interfaces.

The TAdoDbxConnection class has a ConnectionString property. This class also supports connection pooling.

All errors are handled as exceptions in AdoDbx Client in TAdoDbxException, so these classes are not needed.

These classes are implementations of ADO.NET classes. These classes are also implemented in AdoDbx Client. Most source code using these classes should convert to AdoDbx Client with little effort. 

Conversion of BDP classes in this group is fairly straightforward. Check the documentation to see if the method you've used is supported in the corresponding AdoDbx Client class. If it is, you probably don't need to do anything. If the method is not supported, then you need to modify your code to use methods that are supported in either AdoDbx Client or ADO.NET itself. 

The following table shows the correspondence between classes in ADO.NET, BDP and AdoDbx Client:  

correspondence between classes in ADO.NET, BDP and AdoDbx Client  

DbResolver is an implementation of the ISQLResolver interface in the Borland.Data.Schema namespace, described later in this topic.

These interfaces are mainly used by driver writers and there is no AdoDbx Client equivalent. You should rewrite the driver using the dbExpress framework.

This namespace contains five interfaces.

The GetProviders method returns a list of data providers. A similar capability is provided by TAdoDbxProviderFactory.CreateDataSourceEnumerator, which creates an enumerator for all providers. There is no analog for the methods GetConnections or GetDbObjectTypes in AdoDbx Client.

Use the GetSchema method in TAdoDbxConnection to get a metadata collection. The Name parameter of GetSchema specifies the kind of metadata to get. The standard names supported by DbConnection.GetSchema are supported in AdoDbx Client. 

In addition, you can specify one of the name constants in TDBXMetaDataCollectionName to get a particular metadata collection. You would then use the corresponding class in the DBXMetaDataNames namespace to get the column information you want for that metadata collection. 

For instance, to get procedure source code in a database, use the constant ProcedureSources to get a DataTable with procedure source information. Use the DBXMetaDataNames classes TDBXProcedureSourcesColumns and TDBXProcedureSourcesIndex with the returned DataTable to access the procedure source information by name or ordinal.

This class resolves SQL commands.  

The closest analog is the TAdoDbxDataAdapter class for ISQLResolver methods. This table shows the properties that correspond to methods.  

ISQLResolver-TAdoDbxDataAdapter correspondence  

For ISQLResolver properties, the closest analog are properties that TAdoDbxCommandBuilder inherits from the ADO.NET class DbCommandBuilder and a TAdoDbxDataReader property.  

ISQLResolver-AdoDbx Client correspondence  

This interface allows you to create a database schema in your own provider. The AdoDbx Client does not provide this capability.

ADO.NET Overview 

.NET Framework Developer's Guide ADO.NET (MSDN) 

TAdoDbxCommand 

TAdoDbxCommandBuilder 

TAdoDbxConnection 

TAdoDbxDataAdapter 

TAdoDbxDataReader 

TAdoDbxException 

TAdoDbxParameter 

TAdoDbxParameterCollection 

TAdoDbxProviderFactory 

TAdoDbxTransaction 

TDBXMetaDataCollectionName