Functions for connecting to data sources using the OLE DB API.
用于使用OLE DBAPI连接到数据源的函数。
OLE DB is a Microsoft technology that is embedded into the Windows operating system.
OLE DB是Microsoft的一种技术，它被嵌入在Windows操作系统中。
Microsoft has provided a document explaining how to migrate applications from OLE DB to ODBC.
微软已经提供了一份文档，说明如何把应用程序从OLE DB迁移到ODBC。
Fortunately, there are OLE DB providers available for most data sources (relational and non-relational).
幸运的是，对于大多数数据源(关系的和非关系的)，都有可用的OLE DB提供程序(provider)。
OLE DB was introduced primarily to provide uniform data access to non-relational data as well as relational data.
之所以要引入OLE DB，主要是为了给非关系型数据和关系型数据提供统一的数据访问。
Shows the OLE DB provider used for this connection.
显示用于此连接的OLE DB提供程序。
Each OLE DB provider defines specific connection information.
每个OLE DB提供程序都定义了特定的连接信息。
Moreover, the paper puts forward one method based on OLE DB technology.
其次，提出了基于OLE DB技术的异构数据集成方法。
OLE DB has properties for each of the optional interfaces off the rowset object.
OLE DB对行集合对象的每个可选接口都具有属性。
Any tabular data is viewable through OLE DB regardless of whether it came from a database.
任何表格式资料都可透过OLE DB来检视，而不管它是否来自资料库。
Test the provider using a consumer application written with the OLE DB consumer templates.
使用以ole db使用者模板编写的使用者应用程序测试提供程序。
All the OLE DB provider classes are thread-safe, and registry entries are set accordingly.
所有ole DB提供程序类都是线程安全的，并且相应地设置注册表项。
The ATL OLE DB Consumer Wizard lets you specify whether you want a command or table object.
ATLOLE DB使用者向导使您可以指定是否需要命令或表对象。
ADO is a COM wrapper of OLE DB that facilitates writing data access applications (consumers).
ado是ole DB的COM包装，有利于编写数据访问应用程序(使用者)。
The following table shows the mandatory and optional interfaces defined by OLE DB for a rowset object.
下表显示ole db为行集合对象定义的强制和可选接口。
The following table shows the mandatory and optional interfaces defined by OLE DB for a session object.
下表显示ole DB为会话对象定义的强制和可选接口。
The main reason to create an OLE DB provider is to take advantage of the Universal Data Access strategy.
建立OLE DB提供者主要是为了运用通用资料存取策略。
The simplest type of provider supported by the OLE DB templates is a read-only provider with no commands.
OLE DB样板支援的最简单提供者类型为不含命令的唯读提供者。
The following table shows the mandatory and optional interfaces defined by OLE DB for a transaction object.
下表显示ole DB为事务对象定义的强制和可选接口。
Provides links to conceptual topics discussing the OLE DB database technology and the OLE DB Template Library.
提供指向讨论ole DB数据库技术和OLE DB模板库的概念性主题的链接。
Run the OLE DB conformance tests (including ADO conformance tests) to ensure that your provider meets the level 0 standard for OLE DB providers.
运行ole DB一致性测试(包括ADO一致性测试)，确保提供程序符合OLE DB提供程序的级别0标准。
This provider implements both the OLE DB specification and the specification's extensions for online analytical processing (OLAP) and data mining.
该提供者实现了OLE DB的规范，以及联机分析处理(OLAP)和数据挖掘的扩展规范。
The goal of OLE DB (as was the goal of ODBC before it) is to provide transparent access to a variety of relational and non-relational data sources.
OLE DB的目标（就像它之前的ODBC 的目标）是提供对各种关系和非关系数据源的透明的访问。
Thus, a provider is any software component that implements OLE DB interfaces to encapsulate access to data and expose it to other objects (that is, consumers).
因此，提供程序是指任何一个实现OLE DB接口来封装数据访问并将其向其他对象(即，使用者)公开的软件组件。
OLE DB is a COM-based universal data access technology, allowing you to use any data source, not just indexed, sequential access methods (ISAM) and SQL-based databases.
OLE DB是基于COM的通用数据访问方法，允许使用任何数据源，不只是已索引的、连续的访问方法(ISAM)和基于SQL的数据库。
OLE DB providers can access data from a variety of data sources and is not limited to SQL queries to retrieve data but rather can use queries as defined in the provider.
OLE DB提供程序可以从各种不同的数据源访问数据，而且并不仅限于用SQL查询来检索数据，而是可以使用提供程序中定义的任何查询。
Based on the COM specification, OLE DB defines an extensible and maintainable collection of interfaces that factor and encapsulate consistent, reusable portions of DBMS functionality.
OLE DB根据COM的规格，定义了一个可扩充和维护的介面集合，此集合可将DBMS的功能分解并包装成一致、可重复使用的部分。
OLE DB access is great (and needed), but most of today's data doesn't actually exist in nicely formatted rows and columns (which sometimes gets lost when we talk about relational databases so much).
OLE DB访问很伟大(也是很必要的)，但如今大多数数据并不是规规矩矩地就放在行和列之中(当我们大肆谈论关系数据库时，这一事实有时候竟被遗忘了)。
OLE DB access is great (and needed), but most of today's data doesn't actually exist in nicely formatted rows and columns (which sometimes gets lost when we talk about relational databases so much).
OLE DB访问很伟大(也是很必要的)，但如今大多数数据并不是规规矩矩地就放在行和列之中(当我们大肆谈论关系数据库时，这一事实有时候竟被遗忘了)。
应用推荐