Shows the OLE DB provider used for this connection.
显示用于此连接的OLE DB提供程序。
Each OLE DB provider defines specific connection information.
每个OLE DB提供程序都定义了特定的连接信息。
Functions for connecting to data sources using the OLE DB API.
用于使用OLE DBAPI连接到数据源的函数。
Each class is based on a standard OLE DB component implementation.
每个类别都是根据标准ole DB元件的实作。
Some OLE DB providers can check the current state of the connection.
一些OLE DB提供程序可以检查连接的当前状态。
The session object is the primary link to get to OLE DB functionality.
工作阶段物件是取得OLE DB 功能的主要连结。
Moreover, the paper puts forward one method based on OLE DB technology.
其次，提出了基于OLE DB技术的异构数据集成方法。
By default, the wizards generate code that is OLE DB level 0 compliant.
根据预设，精灵可产生与ole db层级0相容的程序码。
The OLE DB Provider Template Architecture describes these interfaces in detail.
如需这些介面的详细资讯，请参阅 OLE DB提供者样板架构。
OLE DB has properties for each of the optional interfaces off the rowset object.
OLE DB对行集合对象的每个可选接口都具有属性。
OLE DB is a Microsoft technology that is embedded into the Windows operating system.
OLE DB是Microsoft的一种技术，它被嵌入在Windows操作系统中。
It can actually be used to retrieve data from any OLE DB or ODBC-compliant data source.
它实际上可以用来从任何ole DB或符合ODBC的数据源中检索数据。
Any tabular data is viewable through OLE DB regardless of whether it came from a database.
任何表格式资料都可透过OLE DB来检视，而不管它是否来自资料库。
All the OLE DB provider classes are thread-safe, and registry entries are set accordingly.
所有ole DB提供程序类都是线程安全的，并且相应地设置注册表项。
Test the provider using a consumer application written with the OLE DB consumer templates.
使用以ole db使用者模板编写的使用者应用程序测试提供程序。
The ATL OLE DB Consumer Wizard lets you specify whether you want a command or table object.
ATLOLE DB使用者向导使您可以指定是否需要命令或表对象。
Microsoft has provided a document explaining how to migrate applications from OLE DB to ODBC.
微软已经提供了一份文档，说明如何把应用程序从OLE DB迁移到ODBC。
ADO is a COM wrapper of OLE DB that facilitates writing data access applications (consumers).
ado是ole DB的COM包装，有利于编写数据访问应用程序(使用者)。
For information about the attributes discussed in this topic, see OLE DB Consumer attributes.
有关本主题中所讨论特性的信息，请参见ole db使用者特性。
Fortunately, there are OLE DB providers available for most data sources (relational and non-relational).
幸运的是，对于大多数数据源(关系的和非关系的)，都有可用的OLE DB提供程序(provider)。
The main reason to create an OLE DB provider is to take advantage of the Universal Data Access strategy.
建立OLE DB提供者主要是为了运用通用资料存取策略。
To see the result of all this work, open the "OLE DB Data Source State" view within the monitoring pane.
看到这一切工作的结果，打开“OLE DB数据源的状态”窗格视图内的监测。
The simplest type of provider supported by the OLE DB templates is a read-only provider with no commands.
OLE DB样板支援的最简单提供者类型为不含命令的唯读提供者。
If you are using the ODBC OLE DB provider, as shown in the following example, the buffer must be 4 bytes.
如果您正在使用ODBCOLE DB提供者(如下列范例所示)，该缓冲区必须是4个位元组。
Provides links to conceptual topics discussing the OLE DB database technology and the OLE DB Template Library.
提供指向讨论ole DB数据库技术和OLE DB模板库的概念性主题的链接。
OLE DB was introduced primarily to provide uniform data access to non-relational data as well as relational data.
之所以要引入OLE DB，主要是为了给非关系型数据和关系型数据提供统一的数据访问。
ADO mostly includes RDO-style functionality to interact with OLE DB data sources, plus remoting and DHTML technology.
ADO主要包含了RDO风格的、与ole DB数据源交互的功能，并附加远程和DHTML技术。
This native provider provides an improved level of support over the ODBC and OLE DB generic managed providers for DB2.
它为DB 2提供了更好级别的支持，胜过DB2的odbc和ole DB通用(generic)托管提供程序。
By using OLE DB providers, you can keep data in its native format and still be able to access it in a simple operation.
您可透过使用OLE DB提供者，让资料保持其原型格式，并仍可使用简单作业存取。
By using OLE DB providers, you can keep data in its native format and still be able to access it in a simple operation.
您可透过使用OLE DB提供者，让资料保持其原型格式，并仍可使用简单作业存取。
应用推荐