You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/data/oledb/accessors-and-rowsets.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Accessors and Rowsets | Microsoft Docs"
3
3
ms.custom: ""
4
-
ms.date: "11/04/2016"
4
+
ms.date: "10/22/2018"
5
5
ms.technology: ["cpp-data"]
6
6
ms.topic: "reference"
7
7
dev_langs: ["C++"]
@@ -26,7 +26,7 @@ Accessor Classes
26
26
27
27
-[CAccessor](../../data/oledb/caccessor-class.md) Use this accessor when you know the structure of the database source at design time. `CAccessor` statically binds a database record, which contains the buffer, to the data source.
28
28
29
-
-[CDynamicAccessor](../../data/oledb/cdynamicaccessor-class.md) Use this accessor when you do not know the structure of the database at design time. `CDynamicAccessor` calls `IColumnsInfo::GetColumnInfo` to get the database column information. It creates and manages an accessor and the buffer.
29
+
-[CDynamicAccessor](../../data/oledb/cdynamicaccessor-class.md) Use this accessor when you don't know the structure of the database at design time. `CDynamicAccessor` calls `IColumnsInfo::GetColumnInfo` to get the database column information. It creates and manages an accessor and the buffer.
30
30
31
31
-[CDynamicParameterAccessor](../../data/oledb/cdynamicparameteraccessor-class.md) Use this accessor to handle unknown command types. When you prepare the commands, `CDynamicParameterAccessor` can get parameter information from the `ICommandWithParameters` interface, if the provider supports `ICommandWithParameters`.
32
32
@@ -53,7 +53,7 @@ The following figure shows the rowset types.
[Schema rowsets](../../data/oledb/obtaining-metadata-with-schema-rowsets.md)do not access data in the data store but instead access information about the data store, called metadata. Schema rowsets are typically used in situations in which the database structure is not known at compile time and must be obtained at run time.
56
+
[Schema rowsets](../../data/oledb/obtaining-metadata-with-schema-rowsets.md)don't access data in the data store but instead access information about the data store, called metadata. Schema rowsets are typically used in situations in which the database structure isn't known at compile time and must be obtained at run time.
Copy file name to clipboardExpand all lines: docs/data/oledb/commands-and-tables.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Commands and Tables | Microsoft Docs"
3
3
ms.custom: ""
4
-
ms.date: "11/04/2016"
4
+
ms.date: "10/22/2018"
5
5
ms.technology: ["cpp-data"]
6
6
ms.topic: "reference"
7
7
dev_langs: ["C++"]
@@ -18,7 +18,7 @@ Commands and tables allow you to access rowsets; that is, open rowsets, execute
18
18
![CCommand and CTable](../../data/oledb/media/vccommandstables.gif"vccommandstables")
19
19
Command and Table Classes
20
20
21
-
In the previous table, `TAccessor` can be any accessor type listed in [Accessor Types](../../data/oledb/accessors-and-rowsets.md). *TRowset* can be any rowset type listed in [Rowset Types](../../data/oledb/accessors-and-rowsets.md). *TMultiple* specifies the result type (a single or multiple result set).
21
+
In the previous table, `TAccessor` can be any accessor type listed in [Accessor Types](../../data/oledb/accessors-and-rowsets.md). `TRowset` can be any rowset type listed in [Rowset Types](../../data/oledb/accessors-and-rowsets.md). `TMultiple` specifies the result type (a single or multiple result set).
22
22
23
23
The [ATL OLE DB Consumer Wizard](../../atl/reference/atl-ole-db-consumer-wizard.md) lets you specify whether you want a command or table object.
This procedure demonstrates how you can use the ATL Project Wizard and ATL OLE DB Consumer Wizard to generate an OLE DB Templates consumer and then modify the main code of the console application to retrieve and display data from a database table.
16
+
This procedure demonstrates how you can use the **ATL Project Wizard** and **ATL OLE DB Consumer Wizard* to generate an OLE DB Templates consumer and then modify the main code of the console application to retrieve and display data from a database table.
17
17
18
18
The last two sections explain the wizard-generated OLE DB consumer code.
You can create an OLE DB Templates consumer with or without the ATL OLE DB Consumer Wizard, though using the wizard is the recommended method. A consumer can operate in any application that supports ATL.
16
+
You can create an OLE DB Templates consumer with or without the **ATL OLE DB Consumer Wizard**, though using the wizard is the recommended method. A consumer can operate in any application that supports ATL.
Copy file name to clipboardExpand all lines: docs/data/oledb/data-sources-and-sessions.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Data Sources and Sessions | Microsoft Docs"
3
3
ms.custom: ""
4
-
ms.date: "11/04/2016"
4
+
ms.date: "10/22/2018"
5
5
ms.technology: ["cpp-data"]
6
6
ms.topic: "reference"
7
7
dev_langs: ["C++"]
@@ -22,7 +22,7 @@ The classes are:
22
22
23
23
-[CDataSource](../../data/oledb/cdatasource-class.md) This class instantiates the data source object, which creates and manages a connection to a data source through an OLE DB provider. The data source takes information such as the data source address and authentication information in the form of a connection string.
24
24
25
-
It is also worth noting that the helper class [CEnumerator](../../data/oledb/cenumerator-class.md) is often used before any connection is established to obtain a list of available providers registered on a system. This allows you to select a provider as a data source. For example, the **Data Link Properties** dialog box uses this class to populate the list of providers on the **Providers** tab. It is equivalent to the `SQLBrowseConnect` or `SQLDriverConnect` function.
25
+
It's also worth noting that the helper class [CEnumerator](../../data/oledb/cenumerator-class.md) is often used before any connection is established to obtain a list of available providers registered on a system. This allows you to select a provider as a data source. For example, the **Data Link Properties** dialog box uses this class to populate the list of providers on the **Providers** tab. It equates to the `SQLBrowseConnect` or `SQLDriverConnect` function.
26
26
27
27
-[CSession](../../data/oledb/csession-class.md) This class instantiates the session object, which represents a single access session to the data source. However, you can create multiple sessions on a data source. For each session, you can create rowsets, commands, and other objects to access data from the data source. The session handles transactions.
You should consider the following issues before starting your OLE DB application:
16
+
Consider the following issues before starting your OLE DB application:
17
17
18
18
## What programming implementation will you use to write your OLE DB application?
19
19
20
-
Microsoft offers several libraries to accomplish this: an OLE DB Template library, OLE DB attributes, and the raw OLE DB interfaces in the OLE DB SDK. In addition, there are wizards that help you write your program. These implementations are described in [OLE DB Templates, Attributes, and Other Implementations](../../data/oledb/ole-db-templates-attributes-and-other-implementations.md).
20
+
Microsoft offers several libraries to accomplish this task: an OLE DB Template library, OLE DB attributes, and the raw OLE DB interfaces in the OLE DB SDK. Also, there are wizards that help you write your program. These implementations are described in [OLE DB Templates, Attributes, and Other Implementations](../../data/oledb/ole-db-templates-attributes-and-other-implementations.md).
21
21
22
22
## Do you need to write your own provider?
23
23
24
-
Most developers do not need to write their own provider. Microsoft provides several providers. Whenever you create a data connection (for example, when you add a consumer to your project using the ATL OLE DB Consumer Wizard), the **Data Link Properties** dialog box lists all the available providers registered on your system. If one of these providers is appropriate for your own data store and data access application, the easiest thing to do is use one of these. However, if your data store does not fit one of these categories, you have to create your own provider. For information about creating providers, see [OLE DB Provider Templates](../../data/oledb/ole-db-provider-templates-cpp.md).
24
+
Most developers don't need to write their own provider. Microsoft provides several providers. Whenever you create a data connection (for example, when you add a consumer to your project using the **ATL OLE DB Consumer Wizard**), the **Data Link Properties** dialog box lists all the available providers registered on your system. If one of the providers is appropriate for your own data store and data access application, the easiest thing to do is to use one of these. However, if your data store doesn't fit one of these categories, you have to create your own provider. For information about creating providers, see [OLE DB Provider Templates](../../data/oledb/ole-db-provider-templates-cpp.md).
25
25
26
26
## What level of support do you need for your consumer?
27
27
28
-
Some consumers can be very basic; while others can be very complex. The functionality of OLE DB objects is specified by properties. When you use the ATL OLE DB Consumer Wizard to create a consumer or the Database Provider Wizard to create a provider, it sets the appropriate object properties for you to give you a standard set of functionalities. However, if the wizard-generated consumer or provider classes do not support everything you need them to do, you need to refer to the interfaces for those classes in the [OLE DB Templates Library](../../data/oledb/ole-db-templates.md). These interfaces wrap the raw OLE DB interfaces, providing extra implementation to make using them easier for you.
28
+
Some consumers can be basic; while others can be complex. The functionality of OLE DB objects is specified by properties. When you use the **ATL OLE DB Consumer Wizard** to create a consumer or the **Database Provider Wizard** to create a provider, it sets the appropriate object properties for you to give you a standard set of functionalities. However, if the wizard-generated consumer or provider classes don't support everything you need them to do, you need to refer to the interfaces for those classes in the [OLE DB Templates Library](../../data/oledb/ole-db-templates.md). These interfaces wrap the raw OLE DB interfaces, providing extra implementation to make using them easier for you.
29
29
30
30
For example, if you want to update data in a rowset, but forgot to specify this when you created the consumer with the wizard, you can specify the functionality after the fact by setting the `DBPROP_IRowsetChange` and `DBPROP_UPDATABILITY` properties on the command object. Then, when the rowset is created, it has the `IRowsetChange` interface.
31
31
32
32
## Do you have older code using another data access technology (ADO, ODBC, or DAO)?
33
33
34
-
Given the possible combinations of technologies (such as using ADO components with OLE DB components and migrating ODBC code to OLE DB), covering all situations is beyond the scope of the Visual C++ documentation. However, many articles covering various scenarios are available on the following Microsoft Web sites:
34
+
Given the possible combinations of technologies (such as using ADO components with OLE DB components and migrating ODBC code to OLE DB), covering all situations is beyond the scope of the Visual C++ documentation. However, many articles covering various scenarios are available on the following Microsoft web sites:
35
35
36
36
-[Microsoft Help and Support](https://support.microsoft.com/)
The OLE DB Consumer Templates support the OLE DB version 2.6 specification. (The OLE DB Consumer Templates are tested against OLE DB 2.6 but do not support every interface in the specification.) The Consumer Templates minimize the amount of code you must write to implement an OLE DB consumer. The templates provide:
16
+
The OLE DB Consumer Templates support the OLE DB version 2.6 specification. (The OLE DB Consumer Templates are tested against OLE DB 2.6 but don't support every interface in the specification.) The Consumer Templates minimize the amount of code you must write to implement an OLE DB consumer. The templates provide:
17
17
18
18
- Easy access to OLE DB features and easy integration with ATL and MFC.
19
19
20
20
- An easy binding model for database parameters and columns.
21
21
22
22
- Native C/C++ data types for OLE DB programming.
23
23
24
-
To use the OLE DB Templates, you should be familiar with C++ templates, COM, and the OLE DB interfaces. If you are not familiar with OLE DB, see [OLE DB Programmer's Reference](/previous-versions/windows/desktop/ms718124).
24
+
To use the OLE DB Templates, you should be familiar with C++ templates, COM, and the OLE DB interfaces. If you aren't familiar with OLE DB, see [OLE DB Programmer's Reference](/previous-versions/windows/desktop/ms718124).
25
25
26
26
The OLE DB Templates support the existing OLE DB object model rather than adding a new object model. The top-layer classes in the OLE DB Consumer Templates parallel the components defined in the OLE DB specification. The design of the OLE DB Consumer Templates includes advanced features such as multiple accessors on a rowset. The use of templates and multiple inheritance makes the library small and flexible.
27
27
@@ -57,5 +57,5 @@ For more information, see the following topics:
57
57
58
58
[OLE DB Programming](../../data/oledb/ole-db-programming.md)<br/>
59
59
[Data Access](../data-access-in-cpp.md)<br/>
60
-
[OLE DB SDK Documentation](/previous-versions/windows/desktop/ms722784)
60
+
[OLE DB SDK Documentation](/previous-versions/windows/desktop/ms722784)<br/>
61
61
[OLE DB Programmer's Reference](/previous-versions/windows/desktop/ms713643)
The OLE DB architecture uses the model of consumers and providers. A consumer makes requests for data. A provider responds to these requests by placing data in a tabular format and returning it to the consumer. Any call that the consumer can make must be implemented in the provider.
17
17
18
-
Technically defined, a consumer is any system or application code (not necessarily an OLE DB component) that accesses data through OLE DB interfaces. The interfaces are implemented in a provider. 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).
18
+
Technically defined, a consumer is any system or application code (not necessarily an OLE DB component) that accesses data through OLE DB interfaces. The interfaces are implemented in a provider. So 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).
19
19
20
-
In terms of roles, a consumer calls methods on OLE DB interfaces; an OLE DB provider implements the needed OLE DB interfaces.
20
+
For roles, a consumer calls methods on OLE DB interfaces; an OLE DB provider implements the needed OLE DB interfaces.
21
21
22
-
OLE DB avoids the terms client and server because these roles do not always make sense, especially in an n-tier situation. Because a consumer could be a component on a tier that serves another component, to call it a client component would be confusing. Also, a provider sometimes acts more like a database driver than a server.
22
+
OLE DB avoids the terms client and server because these roles don't always make sense, especially in an n-tier situation. Because a consumer could be a component on a tier that serves another component, to call it a client component would be confusing. Also, a provider sometimes acts more like a database driver than a server.
0 commit comments