initial formatting

msebolt · msebolt · commit b60ed4ca5adc · 2018-10-22T10:08:32.000-07:00
diff --git a/docs/data/oledb/creating-a-project-for-the-provider.md b/docs/data/oledb/creating-a-project-for-the-provider.md
@@ -1,7 +1,7 @@
 ---
 title: "Creating a Project for the Provider | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "10/22/2018"
 ms.technology: ["cpp-data"]
 ms.topic: "reference"
 dev_langs: ["C++"]
@@ -19,7 +19,10 @@ ms.workload: ["cplusplus", "data-storage"]
   
      The **New Project** dialog box appears.  
   
-1. In the **Project Types** pane, click the **Visual C++ Projects** folder. In the **Templates** pane, click **ATL Project**.  
+1. In the **Project Types** pane, click the **Installed** > **Visual C++** > **MFC/ATL** folder. In the **Templates** pane, click **ATL Project**.  
+
+    > [!NOTE]
+    > In previous versions of Visual Studio, find the project type under **Installed** > **Templates** > **Visual C++** > **ATL**.
   
 1. In the **Name** box, enter a name for the project, and then click **OK**.  
   
diff --git a/docs/data/oledb/creating-an-updatable-provider.md b/docs/data/oledb/creating-an-updatable-provider.md
@@ -20,7 +20,7 @@ This topic assumes that you are starting with a workable provider. There are two
 Next, you must make sure your provider contains all the functionality to support anything the consumer might request of it. If the consumer wants to update the data store, the provider has to contain code that persists data to the data store. For example, you might use the C Run-Time Library or MFC to perform such operations on your data source. The section "[Writing to the Data Source](#vchowwritingtothedatasource)" describes how to write to the data source, deal with NULL and default values, and set column flags.  
   
 > [!NOTE]
->  [UpdatePV](https://github.com/Microsoft/VCSamples/tree/master/VC2010Samples/ATL/OLEDB/Provider/UPDATEPV) is an example of an updatable provider. UpdatePV is the same as MyProv but with updatable support.  
+> [UpdatePV](https://github.com/Microsoft/VCSamples/tree/master/VC2010Samples/ATL/OLEDB/Provider/UPDATEPV) is an example of an updatable provider. UpdatePV is the same as MyProv but with updatable support.  
   
 ##  <a name="vchowmakingprovidersupdatable"></a> Making Providers Updatable  
 
@@ -34,7 +34,7 @@ You must first decide whether to inherit from `IRowsetChangeImpl` or `IRowsetUpd
   
 Note that `IRowsetUpdateImpl` derives from `IRowsetChangeImpl`. Thus, `IRowsetUpdateImpl` gives you change capability plus batch capability.  
   
-#### To support updatability in your provider  
+### To support updatability in your provider  
   
 1. In your rowset class, inherit from `IRowsetChangeImpl` or `IRowsetUpdateImpl`. These classes provide appropriate interfaces for changing the data store:  
   
@@ -57,7 +57,7 @@ Note that `IRowsetUpdateImpl` derives from `IRowsetChangeImpl`. Thus, `IRowsetUp
     ```  
   
     > [!NOTE]
-    >  You should remove the `IRowsetChangeImpl` line from your inheritance chain. This one exception to the directive previously mentioned must include the code for `IRowsetChangeImpl`.  
+    > You should remove the `IRowsetChangeImpl` line from your inheritance chain. This one exception to the directive previously mentioned must include the code for `IRowsetChangeImpl`.  
   
 1. Add the following to your COM map (`BEGIN_COM_MAP ... END_COM_MAP`):  
   
@@ -96,7 +96,7 @@ Note that `IRowsetUpdateImpl` derives from `IRowsetChangeImpl`. Thus, `IRowsetUp
      You can find the values used in these macro calls by looking in Atldb.h for the property IDs and values (if Atldb.h differs from the online documentation, Atldb.h supersedes the documentation).  
   
     > [!NOTE]
-    >  Many of the `VARIANT_FALSE` and `VARIANT_TRUE` settings are required by the OLE DB templates; the OLE DB specification says they can be read/write, but the OLE DB templates can only support one value.  
+    > Many of the `VARIANT_FALSE` and `VARIANT_TRUE` settings are required by the OLE DB templates; the OLE DB specification says they can be read/write, but the OLE DB templates can only support one value.  
   
      **If you implement IRowsetChangeImpl**  
   
@@ -129,16 +129,14 @@ Note that `IRowsetUpdateImpl` derives from `IRowsetChangeImpl`. Thus, `IRowsetUp
     - `DBPROP_MAXPENDINGROWS`.  
   
         > [!NOTE]
-        >  If you support notifications, you might also have some other properties as well; see the section on `IRowsetNotifyCP` for this list.  
+        > If you support notifications, you might also have some other properties as well; see the section on `IRowsetNotifyCP` for this list.  
   
 ##  <a name="vchowwritingtothedatasource"></a> Writing to the Data Source  
 
 To read from the data source, call the `Execute` function. To write to the data source, call the `FlushData` function. (In a general sense, flush means to save modifications you make to a table or index to disk.)  
 
 ```cpp
-
 FlushData(HROW, HACCESSOR);  
-
 ```
 
 The row handle (HROW) and accessor handle (HACCESSOR) arguments allow you to specify the region to write. Typically, you write a single data field at a time.
@@ -179,7 +177,7 @@ Handling NULL values.
 
 ### Handling default values.
 
-To implement your own FlushData method, you need to:
+To implement your own `FlushData` method, you need to:
 
 - Go to your rowset class.
 
@@ -194,7 +192,7 @@ To implement your own FlushData method, you need to:
 
 - Provide an implementation of `FlushData`.
 
-A good implementation of FlushData stores only the rows and columns that are actually updated. You can use the HROW and HACCESSOR parameters to determine the current row and column being stored for optimization.
+A good implementation of `FlushData` stores only the rows and columns that are actually updated. You can use the HROW and HACCESSOR parameters to determine the current row and column being stored for optimization.
 
 Typically, the biggest challenge is working with your own native data store. If possible, try to:
 
@@ -206,7 +204,7 @@ Typically, the biggest challenge is working with your own native data store. If
 
 The best thing to do is to have actual specified values in your data store for NULL and default values. It is best if you can extrapolate this data. If not, you are advised not to allow NULL and default values.
 
-The following example shows how `FlushData` is implemented in the RUpdateRowset class in the UpdatePV sample (see Rowset.h in the sample code):
+The following example shows how `FlushData` is implemented in the `RUpdateRowset` class in the `UpdatePV` sample (see Rowset.h in the sample code):
 
 ```cpp
 ///////////////////////////////////////////////////////////////////////////  
@@ -361,16 +359,15 @@ ATLCOLUMNINFO* CommonGetColInfo(IUnknown* pPropsUnk, ULONG* pcCols, bool bBookma
   
     return _rgColumns;  
 }  
-
 ```
 
 ### Default Values
 
 As with NULL data, you have the responsibility to deal with changing default values.
 
-The default of FlushData and Execute is to return S_OK. Therefore, if you do not override this function, the changes appear to succeed (S_OK will be returned), but they will not be transmitted to the data store.
+The default of `FlushData` and `Execute` is to return S_OK. Therefore, if you do not override this function, the changes appear to succeed (S_OK will be returned), but they will not be transmitted to the data store.
 
-In the UpdatePV sample (in Rowset.h), the `SetDBStatus` method handles default values as follows:
+In the `UpdatePV` sample (in Rowset.h), the `SetDBStatus` method handles default values as follows:
 
 ```cpp
 virtual HRESULT SetDBStatus(DBSTATUS* pdbStatus, CSimpleRow* pRow,  
@@ -409,11 +406,11 @@ virtual HRESULT SetDBStatus(DBSTATUS* pdbStatus, CSimpleRow* pRow,
 
 ### Column Flags
 
-If you support default values on your columns, you need to set it using metadata in the \<provider class\>SchemaRowset class. Set `m_bColumnHasDefault` = VARIANT_TRUE.
+If you support default values on your columns, you need to set it using metadata in the \<provider class\>SchemaRowset class. Set `m_bColumnHasDefault = VARIANT_TRUE`.
 
 You also have the responsibility to set the column flags, which are specified using the DBCOLUMNFLAGS enumerated type. The column flags describe column characteristics.
 
-For example, in the `CUpdateSessionColSchemaRowset` class in UpdatePV (in Session.h), the first column is set up this way:
+For example, in the `CUpdateSessionColSchemaRowset` class in `UpdatePV` (in Session.h), the first column is set up this way:
 
 ```cpp
 // Set up column 1  
diff --git a/docs/data/oledb/debugging-your-provider.md b/docs/data/oledb/debugging-your-provider.md
@@ -19,7 +19,7 @@ There are two ways to debug your provider:
   
 - You can use the ITEST utility that comes with Visual C++.  
   
-### To use the ITEST utility  
+## To use the ITEST utility  
   
 1. Open the provider project.  
   
diff --git a/docs/data/oledb/dynamically-binding-columns-in-your-provider.md b/docs/data/oledb/dynamically-binding-columns-in-your-provider.md
@@ -19,7 +19,7 @@ Make sure you really need dynamic column binding. You might need it because:
   
 - You support an element such as bookmarks that adds columns.  
   
-### To implement dynamic column binding  
+## To implement dynamic column binding  
   
 1. Remove any `PROVIDER_COLUMN_MAP`s from your code.  
   
diff --git a/docs/data/oledb/dynamically-determining-columns-returned-to-the-consumer.md b/docs/data/oledb/dynamically-determining-columns-returned-to-the-consumer.md
@@ -15,11 +15,11 @@ ms.workload: ["cplusplus", "data-storage"]
 
 The PROVIDER_COLUMN_ENTRY macros normally handle the `IColumnsInfo::GetColumnsInfo` call. However, because a consumer might choose to use bookmarks, the provider must be able to change the columns returned depending on whether the consumer asks for a bookmark.  
   
-To handle the `IColumnsInfo::GetColumnsInfo` call, delete the PROVIDER_COLUMN_MAP, which defines a function `GetColumnInfo`, from the `CAgentMan` user record in MyProviderRS.h and replace it with the definition for your own `GetColumnInfo` function:  
+To handle the `IColumnsInfo::GetColumnsInfo` call, delete the PROVIDER_COLUMN_MAP, which defines a function `GetColumnInfo`, from the `CAgentMan` user record in *Custom*RS.h and replace it with the definition for your own `GetColumnInfo` function:  
   
 ```cpp
 ////////////////////////////////////////////////////////////////////////  
-// MyProviderRS.H  
+// CustomRS.H  
 class CAgentMan  
 {  
 public:  
@@ -40,13 +40,13 @@ public:
   
 Next, implement the `GetColumnInfo` function in MyProviderRS.cpp, as shown in the following code.  
   
-`GetColumnInfo` checks first to see if the OLE DB property `DBPROP_BOOKMARKS` is set. To get the property, `GetColumnInfo` uses a pointer (`pRowset`) to the rowset object. The `pThis` pointer represents the class that created the rowset, which is the class where the property map is stored. `GetColumnInfo` typecasts the `pThis` pointer to an `RMyProviderRowset` pointer.  
+`GetColumnInfo` checks first to see if the OLE DB property `DBPROP_BOOKMARKS` is set. To get the property, `GetColumnInfo` uses a pointer (`pRowset`) to the rowset object. The `pThis` pointer represents the class that created the rowset, which is the class where the property map is stored. `GetColumnInfo` typecasts the `pThis` pointer to an `RCustomRowset` pointer.  
   
 To check for the `DBPROP_BOOKMARKS` property, `GetColumnInfo` uses the `IRowsetInfo` interface, which you can obtain by calling `QueryInterface` on the `pRowset` interface. As an alternative, you can use an ATL [CComQIPtr](../../atl/reference/ccomqiptr-class.md) method instead.  
   
 ```cpp
 ////////////////////////////////////////////////////////////////////  
-// MyProviderRS.cpp  
+// CustomRS.cpp  
 ATLCOLUMNINFO* CAgentMan::GetColumnInfo(void* pThis, ULONG* pcCols)  
 {  
    static ATLCOLUMNINFO _rgColumns[5];  
@@ -107,7 +107,7 @@ This example uses a static array to contain the column information. If the consu
   
 ```cpp
 ////////////////////////////////////////////////////////////////////////  
-// MyProviderRS.h  
+// CustomRS.h  
   
 #define ADD_COLUMN_ENTRY(ulCols, name, ordinal, colSize, type, precision, scale, guid, dataClass, member) \  
    _rgColumns[ulCols].pwszName = (LPOLESTR)name; \  
diff --git a/docs/data/oledb/modifying-the-inheritance-of-rmyproviderrowset.md b/docs/data/oledb/modifying-the-inheritance-of-rmyproviderrowset.md
@@ -1,25 +1,25 @@
 ---
-title: "Modifying the Inheritance of RMyProviderRowset | Microsoft Docs"
+title: "Modifying the Inheritance of RCustomRowset | Microsoft Docs"
 ms.custom: ""
 ms.date: "11/04/2016"
 ms.technology: ["cpp-data"]
 ms.topic: "reference"
 dev_langs: ["C++"]
-helpviewer_keywords: ["RMyProviderRowset", "inheritance [C++]"]
+helpviewer_keywords: ["RMyProviderRowset", "inheritance [C++]", "RCustomRowset"]
 ms.assetid: 33089c90-98a4-43e7-8e67-d4bb137e267e
 author: "mikeblome"
 ms.author: "mblome"
 ms.workload: ["cplusplus", "data-storage"]
 ---
-# Modifying the Inheritance of RMyProviderRowset
+# Modifying the Inheritance of RCustomRowset
 
-To add the `IRowsetLocate` interface to the simple read-only provider example, modify the inheritance of `RMyProviderRowset`. Initially, `RMyProviderRowset` inherits from `CRowsetImpl`. You need to modify it to inherit from `CRowsetBaseImpl`.  
+To add the `IRowsetLocate` interface to the simple read-only provider example, modify the inheritance of `RCustomRowset`. Initially, `RCustomRowset` inherits from `CRowsetImpl`. You need to modify it to inherit from `CRowsetBaseImpl`.  
   
-To do this, create a new class, `CMyRowsetImpl`, in MyProviderRS.h:  
+To do this, create a new class, `CMyRowsetImpl`, in *Custom*RS.h:  
   
 ```cpp
 ////////////////////////////////////////////////////////////////////////  
-// MyProviderRS.h  
+// CustomRS.h  
   
 template <class T, class Storage, class CreatorClass, class ArrayType = CAtlArray<Storage>>  
 class CMyRowsetImpl:  
@@ -29,7 +29,7 @@ class CMyRowsetImpl:
 };  
 ```  
   
-Now, edit the COM interface map in MyProviderRS.h to be as follows:  
+Now, edit the COM interface map in *Custom*RS.h to be as follows:  
   
 ```cpp  
 BEGIN_COM_MAP(CMyRowsetImpl)  
@@ -43,7 +43,7 @@ This creates a COM interface map that tells `CMyRowsetImpl` to call `QueryInterf
 Finally, link `RAgentRowset` to `CMyRowsetBaseImpl` by modifying `RAgentRowset` to inherit from `CMyRowsetImpl`, as follows:  
   
 ```cpp  
-class RAgentRowset : public CMyRowsetImpl<RAgentRowset, CAgentMan, CMyProviderCommand>  
+class RAgentRowset : public CMyRowsetImpl<RAgentRowset, CAgentMan, CCustomCommand>  
 ```  
   
 `RAgentRowset` can now use the `IRowsetLocate` interface while taking advantage of the rest of the implementation for the rowset class.  
diff --git a/docs/data/oledb/reading-strings-into-the-ole-db-provider.md b/docs/data/oledb/reading-strings-into-the-ole-db-provider.md
@@ -13,22 +13,18 @@ ms.workload: ["cplusplus", "data-storage"]
 ---
 # Reading Strings into the OLE DB Provider
 
-The `RMyProviderRowset::Execute` function opens a file and reads strings. The consumer passes the file name to the provider by calling [ICommandText::SetCommandText](/previous-versions/windows/desktop/ms709757). The provider receives the file name and stores it in the member variable `m_szCommandText`. `Execute` reads the file name from `m_szCommandText`. If the file name is invalid or the file is unavailable, `Execute` returns an error. Otherwise, it opens the file and calls `fgets` to retrieve the strings. For each set of strings it reads, `Execute` creates an instance of the user record (`CAgentMan`) and places it into an array.  
+The `RCustomRowset::Execute` function opens a file and reads strings. The consumer passes the file name to the provider by calling [ICommandText::SetCommandText](/previous-versions/windows/desktop/ms709757). The provider receives the file name and stores it in the member variable `m_szCommandText`. `Execute` reads the file name from `m_szCommandText`. If the file name is invalid or the file is unavailable, `Execute` returns an error. Otherwise, it opens the file and calls `fgets` to retrieve the strings. For each set of strings it reads, `Execute` creates an instance of the user record (`CAgentMan`) and places it into an array.  
   
 If the file cannot be opened, `Execute` must return DB_E_NOTABLE. If it returns E_FAIL instead, the provider will not work with many consumers and will not pass the OLE DB [conformance tests](../../data/oledb/testing-your-provider.md).  
   
 ## Example  
-  
-### Description  
 
 The edited `Execute` function looks like this:  
   
-### Code  
-  
 ```cpp
 /////////////////////////////////////////////////////////////////////////  
-// MyProviderRS.h  
-class RMyProviderRowset : public CRowsetImpl< RMyProviderRowset, CAgentMan, CRMyProviderCommand>  
+// CustomRS.h  
+class RCustomRowset : public CRowsetImpl< RCustomRowset, CAgentMan, CRCustomCommand>  
 {  
 public:  
     HRESULT Execute(DBPARAMS * pParams, LONG* pcRowsAffected)  
diff --git a/docs/data/oledb/referencing-a-property-in-your-provider.md b/docs/data/oledb/referencing-a-property-in-your-provider.md
@@ -51,7 +51,6 @@ HRESULT hr;
 if (spRowsetProps)  
    hr = spRowsetProps->GetProperties(1, &set, &ulPropSet, &pPropSet);  
   
-
 if (pPropSet)  
 {  
    CComVariant var = pPropSet->rgProperties[0].vValue;  
diff --git a/docs/data/oledb/supporting-notifications.md b/docs/data/oledb/supporting-notifications.md
@@ -23,7 +23,7 @@ Note that you must also implement and register `IRowsetNotify` on the consumer (
   
 In addition, the class must also contain a map that defines the connection point entry, like this:  
   
-```  
+```cpp  
 BEGIN_CONNECTION_POINT_MAP  
    CONNECTIONPOINT_ENTRY (IID_IRowsetNotify)  
 END_CONNECTION_POINT_MAP  
@@ -36,7 +36,7 @@ To add `IRowsetNotify`, you need to add `IConnectionPointContainerImpl<rowset-na
 For example, here is the inheritance chain for `RUpdateRowset` in [UpdatePV](https://github.com/Microsoft/VCSamples/tree/master/VC2010Samples/ATL/OLEDB/Provider/UPDATEPV):  
   
 > [!NOTE]
->  The sample code might differ from what is listed here; you should regard the sample code as the more up-to-date version.  
+> The sample code might differ from what is listed here; you should regard the sample code as the more up-to-date version.  
   
 ```cpp
 ///////////////////////////////////////////////////////////////////////////  
@@ -55,7 +55,7 @@ public CRowsetImpl< RUpdateRowset, CAgentMan, CUpdateCommand,
 
 You also need to add the following to the COM map in your rowset:  
   
-```  
+```cpp  
 COM_INTERFACE_ENTRY(IConnectionPointContainer)  
 COM_INTERFACE_ENTRY_IMPL(IConnectionPointContainer)  
 ```  
@@ -66,7 +66,7 @@ These macros allow anyone calling `QueryInterface` for your connection point con
 
 You also need to add a connection point map. It should look something like:  
   
-```  
+```cpp  
 BEGIN_CONNECTION_POINT_MAP(rowset-name)  
      CONNECTION_POINT_ENTRY(_uuidof(IRowsetNotify))  
 END_CONNECTION_POINT_MAP()  
diff --git a/docs/data/oledb/testing-the-read-only-provider.md b/docs/data/oledb/testing-the-read-only-provider.md
diff --git a/docs/data/oledb/using-an-existing-ado-recordset.md b/docs/data/oledb/using-an-existing-ado-recordset.md
diff --git a/docs/data/oledb/using-bookmarks.md b/docs/data/oledb/using-bookmarks.md

Original file line number	Diff line number	Diff line change
`@@ -51,7 +51,6 @@ HRESULT hr;`
`51`	`51`	`if (spRowsetProps)`
`52`	`52`	`hr = spRowsetProps->GetProperties(1, &set, &ulPropSet, &pPropSet);`
`53`	`53`
`54`		`-`
`55`	`54`	`if (pPropSet)`
`56`	`55`	`{`
`57`	`56`	`CComVariant var = pPropSet->rgProperties[0].vValue;`