Merge pull request MicrosoftDocs#2009 from mikeblome/mb-mfc-wizards

GitHubber17 · web-flow · commit db209bcb7cc7 · 2019-05-14T14:42:37.000-07:00
Update database topics for removal of wizards in VS2019
diff --git a/docs/atl/reference/adding-an-atl-active-server-page-component.md b/docs/atl/reference/adding-an-atl-active-server-page-component.md
@@ -1,11 +1,19 @@
 ---
 title: "Adding an ATL Active Server Page Component"
-ms.date: "11/04/2016"
-helpviewer_keywords: ["ASP components, adding", "ASP components", "ATL, ASP components", "ATL ASP components"]
+ms.date: "05/09/2019"
 ms.assetid: 7be2204c-6e58-4099-8892-001b848c8987
 ---
 # Adding an ATL Active Server Page Component
 
+
+::: moniker range="vs-2019"
+
+The ATL Active Server Pages component wizard is not available in Visual Studio 2019 and later.
+
+::: moniker-end
+
+::: moniker range="vs-2017"
+
 To add an Active Template Library (ATL) object to your project, your project must have been created as an ATL COM application or as an MFC application that contains ATL support. You can use the [ATL Project Wizard](../../atl/reference/atl-project-wizard.md) to create an ATL application, you can select **Add ATL Support to MFC** from the [Add Class Dialog Box](../../ide/add-class-dialog-box.md) dialog box, or you can [add an ATL object to your MFC application](../../mfc/reference/adding-atl-support-to-your-mfc-project.md) to implement ATL support for an MFC application.
 
 Active Server Pages components are part of the Internet Information Services architecture, which provides the following advanced Web development features:
@@ -24,6 +32,8 @@ Active Server Pages components are part of the Internet Information Services arc
 
 1. In the [Add Class](../../ide/add-class-dialog-box.md) dialog box, in the **Templates** pane, click **ATL Active Server Page Component**, and then click **Open** to display the [ATL Active Server Page Component Wizard](../../atl/reference/atl-active-server-page-component-wizard.md).
 
+::: moniker-end
+
 ## See also
 
 [Adding a Class](../../ide/adding-a-class-visual-cpp.md)<br/>
diff --git a/docs/atl/reference/adding-an-atl-com-plus-1-0-component.md b/docs/atl/reference/adding-an-atl-com-plus-1-0-component.md
@@ -1,11 +1,19 @@
 ---
 title: "Adding an ATL COM+ 1.0 Component"
-ms.date: "11/04/2016"
-helpviewer_keywords: ["ATL COM+ 1.0", "ATL projects, adding components", "components [C++], adding ATL COM+ 1.0", "objects [C++], supporting ATL COM+ 1.0"]
+ms.date: "05/09/2019"
 ms.assetid: c6c95e64-9ee4-4a6e-8804-5930202ce1b9
 ---
 # Adding an ATL COM+ 1.0 Component
 
+
+::: moniker range="vs-2019"
+
+The ATL COM+ 1.0 Component wizard is not available in Visual Studio 2019 and later.
+
+::: moniker-end
+
+::: moniker range="<=vs-2017"
+
 This wizard adds an object to your project that supports COM+ 1.0 services, including transactions.
 
 ## To add an ATL COM+ 1.0 component to your project
@@ -20,3 +28,7 @@ This wizard adds an object to your project that supports COM+ 1.0 services, incl
 
 [Adding a Class](../../ide/adding-a-class-visual-cpp.md)<br/>
 [Adding a Method](../../ide/adding-a-method-visual-cpp.md)
+
+::: moniker-end
+
+
diff --git a/docs/atl/reference/adding-objects-and-controls-to-an-atl-project.md b/docs/atl/reference/adding-objects-and-controls-to-an-atl-project.md
@@ -1,12 +1,15 @@
 ---
 title: "Adding Objects and Controls to an ATL Project"
-ms.date: "11/04/2016"
+ms.date: "05/09/2019"
 f1_keywords: ["vc.appwiz.ATL.controls"]
 helpviewer_keywords: ["ATL projects, adding objects", "wizards [C++], ATL projects", "ATL projects, adding controls", "controls [ATL], adding to projects", "objects [C++], adding to ATL projects", "ATL Control Wizard"]
 ms.assetid: c0adcbd0-07fe-4c55-a8fd-8c2c65ecdaad
 ---
 # Adding Objects and Controls to an ATL Project
 
+> [!NOTE] 
+> The ATL COM+ 1.0 Component Wizard, ATL OLE DB Consumer wizard, and ATL Active Server Page Component wizard are not available in Visual Studio 2019 and later.
+
 You can use one of the ATL code wizards to add an object or a control to your ATL- or MFC-based projects. For each COM object or control you add, the wizard generates .cpp and .h files, as well as an .rgs file for script-based registry support. The following ATL code wizards are available in Visual Studio:
 
 ||||
diff --git a/docs/atl/reference/com-plus-1-0-atl-com-plus-1-0-component-wizard.md b/docs/atl/reference/com-plus-1-0-atl-com-plus-1-0-component-wizard.md
@@ -1,11 +1,19 @@
 ---
 title: "COM+ 1.0, ATL COM+ 1.0 Component Wizard"
-ms.date: "11/04/2016"
+ms.date: "05/09/2019"
 f1_keywords: ["vc.codewiz.class.atl.mts.options"]
 ms.assetid: 2fbe259c-6be1-4d0e-9cfe-721c75c97cb1
 ---
 # COM+ 1.0, ATL COM+ 1.0 Component Wizard
 
+::: moniker range="vs-2019"
+
+This wizard is not available in Visual Studio 2019 and later.
+
+::: moniker-end
+
+::: moniker range="vs-2017"
+
 Use this page of the ATL COM+ 1.0 Component Wizard to specify interface type and additional interfaces to be supported.
 
 For more information on ATL projects and ATL COM classes, see [ATL COM Desktop Components](../../atl/atl-com-desktop-components.md).
@@ -44,6 +52,8 @@ For more information on ATL projects and ATL COM classes, see [ATL COM Desktop C
    |**Not supported**|Specifies that the object excludes transactions. Adds the component attribute macro custom(TLBATTR_TRANS_NOTSUPP,0) to the .h file (attributed projects) or to the .idl file (nonattributed projects).|
    |**Requires new**|Specifies that the object is always the root of a transaction stream by adding the component attribute macro custom(TLBATTR_TRANS_REQNEW,0) to the .h file (attributed projects) or to the .idl file (nonattributed projects).|
 
+::: moniker-end
+
 ## See also
 
 [ATL COM+ 1.0 Component Wizard](../../atl/reference/atl-com-plus-1-0-component-wizard.md)<br/>
diff --git a/docs/data/odbc/record-field-exchange-working-with-the-wizard-code.md b/docs/data/odbc/record-field-exchange-working-with-the-wizard-code.md
@@ -1,11 +1,14 @@
 ---
 title: "Record Field Exchange: Working with the Wizard Code"
-ms.date: "11/04/2016"
+ms.date: "05/09/2019"
 helpviewer_keywords: ["DoFieldExchange method, overriding", "Unicode, with database classes", "field data members, declaring", "RFX (ODBC), wizard code", "RFX (ODBC), implementing", "field data members", "ODBC, RFX", "m_nParams data member, initializing", "m_nFields data member", "m_nParams data member", "overriding, DoFieldExchange", "m_nFields data member, initializing"]
 ms.assetid: f00d882a-ff1b-4a75-9717-98d8762bb237
 ---
 # Record Field Exchange: Working with the Wizard Code
 
+> [!NOTE] 
+> The MFC ODBC Consumer wizard is not available in Visual Studio 2019 and later. You can still create a consumer manually.
+
 This topic explains the code that the MFC Application Wizard and **Add Class** (as described in [Adding an MFC ODBC Consumer](../../mfc/reference/adding-an-mfc-odbc-consumer.md)) write to support RFX and how you might want to alter that code.
 
 > [!NOTE]
diff --git a/docs/data/odbc/recordset-architecture-odbc.md b/docs/data/odbc/recordset-architecture-odbc.md
@@ -21,6 +21,9 @@ This topic describes the data members that comprise the architecture of a record
 
 ##  <a name="_core_a_sample_class"></a> Sample Class
 
+> [!NOTE] 
+> The MFC ODBC Consumer wizard is not available in Visual Studio 2019 and later. You can still create a consumer manually.
+
 When you use the [MFC ODBC Consumer Wizard](../../mfc/reference/adding-an-mfc-odbc-consumer.md) from **Add Class** wizard to declare a recordset class derived from `CRecordset`, the resulting class has the general structure shown in the following simple class:
 
 ```cpp
diff --git a/docs/data/odbc/recordset-creating-and-closing-recordsets-odbc.md b/docs/data/odbc/recordset-creating-and-closing-recordsets-odbc.md
@@ -1,11 +1,14 @@
 ---
 title: "Recordset: Creating and Closing Recordsets (ODBC)"
-ms.date: "11/04/2016"
+ms.date: "05/09/2019"
 helpviewer_keywords: ["ODBC recordsets, creating", "recordsets, creating", "recordsets, opening", "recordsets, closing", "ODBC recordsets, closing", "ODBC recordsets, opening"]
 ms.assetid: 8d2aac23-4396-4ce2-8c60-5ecf1b360d3d
 ---
 # Recordset: Creating and Closing Recordsets (ODBC)
 
+> [!NOTE] 
+> The MFC ODBC Consumer wizard is not available in Visual Studio 2019 and later. You can still create a consumer manually.
+
 This topic applies to the MFC ODBC classes.
 
 To use a recordset, construct a recordset object and then call its `Open` member function to run the recordset's query and select records. When you finish with the recordset, close and destroy the object.
diff --git a/docs/data/odbc/recordset-declaring-a-class-for-a-predefined-query-odbc.md b/docs/data/odbc/recordset-declaring-a-class-for-a-predefined-query-odbc.md
@@ -1,11 +1,14 @@
 ---
 title: "Recordset: Declaring a Class for a Predefined Query (ODBC)"
-ms.date: "11/04/2016"
+ms.date: "05/09/2019"
 helpviewer_keywords: ["ODBC recordsets, queries", "predefined queries and recordsets", "stored procedures, and recordsets", "recordsets, predefined queries", "recordsets, stored procedures"]
 ms.assetid: d27c4df9-dad2-4484-ba72-92ab0c8ff928
 ---
 # Recordset: Declaring a Class for a Predefined Query (ODBC)
 
+> [!NOTE] 
+> The MFC ODBC Consumer wizard is not available in Visual Studio 2019 and later. You can still create a consumer manually.
+
 This topic applies to the MFC ODBC classes.
 
 This topic explains how to create a recordset class for a predefined query (sometimes called a stored procedure, as in Microsoft SQL Server).
diff --git a/docs/data/odbc/recordset-declaring-a-class-for-a-table-odbc.md b/docs/data/odbc/recordset-declaring-a-class-for-a-table-odbc.md
@@ -1,11 +1,14 @@
 ---
 title: "Recordset: Declaring a Class for a Table (ODBC)"
-ms.date: "11/04/2016"
+ms.date: "05/09/2019"
 helpviewer_keywords: ["ODBC recordsets, declaring class for tables", "recordsets, declaring classes for tables"]
 ms.assetid: 3fe286c2-3f3d-493d-9d8c-762310939d08
 ---
 # Recordset: Declaring a Class for a Table (ODBC)
 
+> [!NOTE] 
+> The MFC ODBC Consumer wizard is not available in Visual Studio 2019 and later. You can still create a consumer manually.
+
 This topic applies to the MFC ODBC classes.
 
 The most common recordset class opens a single table. To declare a recordset class for a single table, use the [MFC ODBC Consumer Wizard](../../mfc/reference/adding-an-mfc-odbc-consumer.md) from **Add Class** and choose each column you want by naming a corresponding recordset field data member.
diff --git a/docs/data/odbc/recordset-dynamically-binding-data-columns-odbc.md b/docs/data/odbc/recordset-dynamically-binding-data-columns-odbc.md
@@ -1,6 +1,6 @@
 ---
 title: "Recordset: Dynamically Binding Data Columns (ODBC)"
-ms.date: "11/19/2018"
+ms.date: "05/09/2019"
 helpviewer_keywords: ["ODBC recordsets [C++], binding columns dynamically", "data binding [C++], recordset columns", "recordsets [C++], binding data", "data binding [C++], columns in recordsets", "columns [C++], binding to recordsets"]
 ms.assetid: bff67254-d953-4ae4-9716-91c348cb840b
 ---
@@ -19,6 +19,9 @@ Recordsets manage binding table columns that you specify at design time, but the
 
 ##  <a name="_core_when_you_might_bind_columns_dynamically"></a> When You Might Bind Columns Dynamically
 
+> [!NOTE] 
+> The MFC ODBC Consumer wizard is not available in Visual Studio 2019 and later. You can still create a consumer manually.
+
 At design time, the MFC Application Wizard or [MFC ODBC Consumer Wizard](../../mfc/reference/adding-an-mfc-odbc-consumer.md) (from **Add Class**) creates recordset classes based on the known tables and columns on your data source. Databases can change between when you design them and later when your application uses those tables and columns at run time. You or another user might add or drop a table or add or drop columns from a table that your application's recordset relies on. This probably is not a concern for all data-access applications, but if it is for yours, how can you cope with changes in the database schema, other than by redesigning and recompiling? The purpose of this topic is to answer that question.
 
 This topic describes the most common case in which you might bind columns dynamically — having begun with a recordset based on a known database schema, you want to handle additional columns at run time. The topic further assumes that the additional columns map to `CString` field data members, the most common case, although suggestions are supplied to help you manage other data types.
diff --git a/docs/data/odbc/recordset-how-recordsets-select-records-odbc.md b/docs/data/odbc/recordset-how-recordsets-select-records-odbc.md
@@ -1,11 +1,14 @@
 ---
 title: "Recordset: How Recordsets Select Records (ODBC)"
-ms.date: "11/04/2016"
+ms.date: "05/09/2019"
 helpviewer_keywords: ["recordsets, selecting records", "record selection, ODBC recordsets", "SQL statements, recordset", "records, selecting", "recordsets, constructing SQL statements", "ODBC recordsets, selecting records"]
 ms.assetid: 343a6a91-aa4c-4ef7-b21f-2f2bfd0d3787
 ---
 # Recordset: How Recordsets Select Records (ODBC)
 
+> [!NOTE] 
+> The MFC ODBC Consumer wizard is not available in Visual Studio 2019 and later. You can still create a consumer manually.
+
 This topic applies to the MFC ODBC classes.
 
 This topic explains:
diff --git a/docs/data/odbc/recordset-obtaining-sums-and-other-aggregate-results-odbc.md b/docs/data/odbc/recordset-obtaining-sums-and-other-aggregate-results-odbc.md
@@ -6,6 +6,9 @@ ms.assetid: 94500662-22a4-443e-82d7-acbe6eca447b
 ---
 # Recordset: Obtaining SUMs and Other Aggregate Results (ODBC)
 
+> [!NOTE] 
+> The MFC ODBC Consumer wizard is not available in Visual Studio 2019 and later. You can still create a consumer manually.
+
 This topic applies to the MFC ODBC classes.
 
 This topic explains how to obtain aggregate results using the following [SQL](../../data/odbc/sql.md) keywords:
diff --git a/docs/data/odbc/recordset-odbc.md b/docs/data/odbc/recordset-odbc.md
@@ -1,6 +1,6 @@
 ---
 title: "Recordset (ODBC)"
-ms.date: "11/04/2016"
+ms.date: "05/09/2019"
 helpviewer_keywords: ["recordsets, snapshots", "recordsets, creating", "dynamic recordsets", "forward-only recordsets", "recordsets, dynasets", "ODBC recordsets, CRecordset objects", "ODBC recordsets", "recordsets, about recordsets", "snapshots, ODBC recordsets", "dynasets"]
 ms.assetid: 333337c5-575e-4d26-b5f6-47166ad7874d
 ---
@@ -19,10 +19,7 @@ A [CRecordset](../../mfc/reference/crecordset-class.md) object represents a set
 An example of a recordset based on a table is "all customers," which accesses a Customer table. An example of a query is "all invoices for Joe Smith." An example of a recordset based on a stored procedure (sometimes called a predefined query) is "all of the delinquent accounts," which invokes a stored procedure in the back-end database. A recordset can join two or more tables from the same data source, but not tables from different data sources.
 
 > [!NOTE]
->  For information about deriving recordset classes with the wizards, see [Adding an MFC ODBC Consumer](../../mfc/reference/adding-an-mfc-odbc-consumer.md) and [Database Support, MFC Application Wizard](../../mfc/reference/database-support-mfc-application-wizard.md).
-
-> [!NOTE]
->  Some ODBC drivers support views of the database. A view in this sense is a query originally created with the SQL `CREATE VIEW` statement. The wizards currently do not support views, but it is possible to code this support yourself.
+>  Some ODBC drivers support views of the database. A view in this sense is a query originally created with the SQL `CREATE VIEW` statement.
 
 ##  <a name="_core_recordset_capabilities"></a> Recordset Capabilities
 
diff --git a/docs/data/odbc/recordset-parameterizing-a-recordset-odbc.md b/docs/data/odbc/recordset-parameterizing-a-recordset-odbc.md
@@ -1,6 +1,6 @@
 ---
 title: "Recordset: Parameterizing a Recordset (ODBC)"
-ms.date: "11/04/2016"
+ms.date: "05/09/2019"
 helpviewer_keywords: ["parameterizing recordsets", "ODBC recordsets, parameterizing", "recordsets, parameterizing", "passing parameters, to queries at runtime"]
 ms.assetid: 7d1dfeb6-5ee0-45e2-aacc-63bc52a465cd
 ---
@@ -83,6 +83,9 @@ Before you create your recordset class, determine what parameters you need, what
 
 #### To parameterize a recordset class
 
+> [!NOTE] 
+> The MFC ODBC Consumer wizard is not available in Visual Studio 2019 and later. You can still create this functionality manually.
+
 1. Run the [MFC ODBC Consumer Wizard](../../mfc/reference/adding-an-mfc-odbc-consumer.md) from **Add Class** to create the class.
 
 1. Specify field data members for the recordset's columns.
diff --git a/docs/data/odbc/selecting-and-manipulating-records.md b/docs/data/odbc/selecting-and-manipulating-records.md
@@ -1,12 +1,15 @@
 ---
 title: "Selecting and Manipulating Records"
-ms.date: "11/04/2016"
+ms.date: "05/09/2019"
 helpviewer_keywords: ["records, selecting", "record selection, MFC ODBC classes", "ODBC recordsets, selecting records"]
 ms.assetid: 7f0b3a4a-9941-4475-a612-9ec8d15b7691
 ---
 # Selecting and Manipulating Records
 
-Normally when you select records from a data source using a SQL **SELECT** statement, you get a result set, which is a set of records from a table or a query. With the database classes, you use a recordset object to select and access the result set. This is an object of an application-specific class that you derive from class [CRecordset](../../mfc/reference/crecordset-class.md). When you define a recordset class, you specify the data source to associate it with, the table to use, and the columns of the table. The MFC Application Wizard or **Add Class** (as described in [Adding an MFC ODBC Consumer](../../mfc/reference/adding-an-mfc-odbc-consumer.md)) creates a class with a connection to a specific data source. The wizards write the [GetDefaultSQL](../../mfc/reference/crecordset-class.md#getdefaultsql) member function of class `CRecordset` to return the table name. For more information about using the wizards to create recordset classes, see [Database Support, MFC Application Wizard](../../mfc/reference/database-support-mfc-application-wizard.md) and [Adding an MFC ODBC Consumer](../../mfc/reference/adding-an-mfc-odbc-consumer.md).
+> [!NOTE] 
+> The MFC ODBC Consumer wizard is not available in Visual Studio 2019 and later. You can still create a consumer manually.
+
+Normally when you select records from a data source using a SQL **SELECT** statement, you get a result set, which is a set of records from a table or a query. With the database classes, you use a recordset object to select and access the result set. This is an object of an application-specific class that you derive from class [CRecordset](../../mfc/reference/crecordset-class.md). When you define a recordset class, you specify the data source to associate it with, the table to use, and the columns of the table. The MFC Application Wizard or **Add Class** (as described in [Adding an MFC ODBC Consumer](../../mfc/reference/adding-an-mfc-odbc-consumer.md)) creates a class with a connection to a specific data source. The wizards write the [GetDefaultSQL](../../mfc/reference/crecordset-class.md#getdefaultsql) member function of class `CRecordset` to return the table name.
 
 Using a [CRecordset](../../mfc/reference/crecordset-class.md) object at run time, you can:
 
diff --git a/docs/data/odbc/sql.md b/docs/data/odbc/sql.md
@@ -1,6 +1,6 @@
 ---
 title: "SQL"
-ms.date: "11/04/2016"
+ms.date: "05/09/2019"
 helpviewer_keywords: ["database classes [C++], SQL statements", "SQL [C++]", "SQL [C++], ODBC", "ODBC [C++], SQL implementation"]
 ms.assetid: e3923bc4-b317-4e0b-afd8-3cd403eb0faf
 ---
@@ -29,6 +29,9 @@ The database classes are implemented with ODBC, which uses SQL in a call-level i
 
 ##  <a name="_core_the_database_classes"></a> Database Classes
 
+> [!NOTE] 
+> The MFC ODBC Consumer wizard is not available in Visual Studio 2019 and later. You can still create a consumer manually.
+
 The database classes are designed to let you manipulate and update data in an existing [data source](../../data/odbc/data-source-odbc.md). The [MFC Application Wizard](../../mfc/reference/database-support-mfc-application-wizard.md), the [MFC ODBC Consumer Wizard](../../mfc/reference/adding-an-mfc-odbc-consumer.md) (accessed through **Add Class**), and the database classes construct most of the SQL statements for you.
 
 The database classes use a portion of SQL known as the Data Manipulation Language (DML). These commands let you work with all or part of the data source, add new records, edit records, and delete records. The following table lists the most common SQL keywords and the ways the database classes use them.
diff --git a/docs/ide/adding-a-class-visual-cpp.md b/docs/ide/adding-a-class-visual-cpp.md
@@ -1,6 +1,6 @@
 ---
 title: "Add a class"
-ms.date: "11/08/2018"
+ms.date: "05/09/2019"
 f1_keywords: ["vc.codewiz.classes.adding", "vc.addclass"]
 helpviewer_keywords: ["ATL projects, adding classes", "classes [C++], creating", "classes [C++], adding", "Add Class dialog box"]
 ms.assetid: c34b5f70-4e72-4faa-ba21-e2b05361c4d9
@@ -69,13 +69,8 @@ There are four categories of **Add Class** templates: .NET, ATL, MFC, and Generi
 |Template|Wizard|
 |--------------|------------|
 |Add ATL Support to MFC|Not available|
-|ATL Active Server Page Component|[ATL active server page component wizard](../atl/reference/atl-active-server-page-component-wizard.md)|
 |ATL Control|[ATL control wizard](../atl/reference/atl-control-wizard.md)|
 |ATL Dialog|[ATL dialog wizard](../atl/reference/atl-dialog-wizard.md)|
-|ATL COM+ 1.0 Component|[ATL COM+ 1.0 component wizard](../atl/reference/atl-com-plus-1-0-component-wizard.md)|
-|ATL OLEDB Consumer|[ATL OLE DB consumer wizard](../atl/reference/atl-ole-db-consumer-wizard.md)|
-|ATL OLEDB Provider|[ATL OLE DB provider wizard](../atl/reference/atl-ole-db-provider-wizard.md)|
-|ATL Property Page|[ATL property page wizard](../atl/reference/atl-property-page-wizard.md)|
 |ATL Simple Object|[ATL simple object wizard](../atl/reference/atl-simple-object-wizard.md)|
 |WMI Event Provider|WMI event provider wizard|
 |WMI Instance Provider|WMI instance provider wizard|
@@ -85,9 +80,6 @@ There are four categories of **Add Class** templates: .NET, ATL, MFC, and Generi
 |Template|Wizard|
 |--------------|------------|
 |MFC Class|[MFC add class wizard](../mfc/reference/mfc-add-class-wizard.md)|
-|MFC Class From ActiveX Control|[Add class from ActiveX control wizard](../ide/add-class-from-activex-control-wizard.md)|
-|MFC Class From TypeLib|[Add class from Typelib wizard](../mfc/reference/add-class-from-typelib-wizard.md)|
-|MFC ODBC Consumer|[MFC ODBC consumer wizard](../mfc/reference/mfc-odbc-consumer-wizard.md)|
 
 #### Generic classes
 
