acrolinx

Author: TylerMSFT

docs/mfc/reference/cdaodatabase-class.md

@@ -10,7 +10,7 @@ helpviewer_keywords: ["CDaoDatabase [MFC], CDaoDatabase", "CDaoDatabase [MFC], C
 Represents a connection to an Access database using Data Access Objects (DAO).
 
 > [!NOTE]
-> DAO is supported through Office 2013. DAO 3.6 is the final version, and it's considered obsolete.
+> Data Access Object (DAO) is supported through Office 2013. DAO 3.6 is the final version, and it's considered obsolete.
 
 ## Syntax
 

docs/mfc/reference/cdaoexception-class.md

@@ -10,7 +10,7 @@ helpviewer_keywords: ["CDaoException [MFC], CDaoException", "CDaoException [MFC]
 Represents an exception condition arising from the MFC database classes based on data access objects (DAO).
 
 > [!NOTE]
-> DAO is supported through Office 2013. DAO 3.6 is the final version, and it's considered obsolete.
+> Data Access Object (DAO) is supported through Office 2013. DAO 3.6 is the final version, and it's considered obsolete.
 
 ## Syntax
 

docs/mfc/reference/cdaoparameterinfo-structure.md

@@ -10,7 +10,7 @@ helpviewer_keywords: ["CDaoParameterInfo structure [MFC]", "DAO (Data Access Obj
 The `CDaoParameterInfo` structure contains information about a parameter object defined for data access objects (DAO).
 
 > [!NOTE]
-> DAO is supported through Office 2013. DAO 3.6 is the final version, and it's considered obsolete.
+> Data Access Object (DAO) is supported through Office 2013. DAO 3.6 is the final version, and it's considered obsolete.
 
 ## Syntax
 

docs/mfc/reference/cdaoquerydef-class.md

@@ -10,7 +10,7 @@ helpviewer_keywords: ["CDaoQueryDef [MFC], CDaoQueryDef", "CDaoQueryDef [MFC], A
 Represents a query definition, or "querydef," usually one saved in a database.
 
 > [!NOTE]
-> DAO is supported through Office 2013. DAO 3.6 is the final version, and it's considered obsolete.
+> Data Access Object (DAO) is supported through Office 2013. DAO 3.6 is the final version, and it's considered obsolete.
 
 ## Syntax
 
@@ -105,7 +105,7 @@ You can use a querydef object for any type of query, including select, action, c
 
 To use a querydef object to create a `CDaoRecordset` object, you typically create or open a querydef as described above. Then construct a recordset object, passing a pointer to your querydef object when you call [`CDaoRecordset::Open`](../../mfc/reference/cdaorecordset-class.md#open). The querydef you pass must be in an open state. For more information, see class [`CDaoRecordset`](../../mfc/reference/cdaorecordset-class.md).
 
-You cannot use a querydef to create a recordset (the most common use for a querydef) unless it's in an open state. Put the querydef into an open state by calling either `Open` or `Create`.
+You can't use a querydef to create a recordset (the most common use for a querydef) unless it's in an open state. Put the querydef into an open state by calling either `Open` or `Create`.
 
 ## External Databases
 
@@ -150,7 +150,7 @@ BOOL CanUpdate();
 
 ### Return Value
 
-Nonzero if you are permitted to modify the querydef; otherwise 0.
+Nonzero if you're permitted to modify the querydef; otherwise 0.
 
 ### Remarks
 
@@ -223,7 +223,7 @@ The SQL string that defines the query. If you accept the default value of NULL,
 
 If you pass a name in *lpszName*, you can then call [Append](#append) to save the querydef in the database's QueryDefs collection. Otherwise, the object is a temporary querydef and isn't saved. In either case, the querydef is in an open state, and you can either use it to create a [CDaoRecordset](../../mfc/reference/cdaorecordset-class.md) object or call the querydef's [Execute](#execute) member function.
 
-If you don't supply a SQL statement in *lpszSQL*, you cannot run the query with `Execute` but you can use it to create a recordset. In that case, MFC uses the recordset's default SQL statement.
+If you don't supply a SQL statement in *lpszSQL*, you can't run the query with `Execute` but you can use it to create a recordset. In that case, MFC uses the recordset's default SQL statement.
 
 ## <a name="execute"></a> CDaoQueryDef::Execute
 
@@ -248,7 +248,7 @@ An integer that determines the characteristics of the query. For related informa
 
 - `dbFailOnError` Default value. Roll back updates if an error occurs and report the error to the user.
 
-- `dbSeeChanges` Generate a run-time error if another user is changing data you are editing.
+- `dbSeeChanges` Generate a run-time error if another user is changing data you're editing.
 
 > [!NOTE]
 > For an explanation of the terms "inconsistent" and "consistent," see the topic "Execute Method" in DAO Help.
@@ -430,7 +430,7 @@ The number of parameters defined in the query.
 
 ### Remarks
 
-`GetParameterCount` is useful for looping through all parameters in the querydef. For that purpose, use `GetParameterCount` in conjunction with [GetParameterInfo](#getparameterinfo).
+`GetParameterCount` is useful for looping through all parameters in the querydef. For that purpose, use `GetParameterCount` with [`GetParameterInfo`](#getparameterinfo).
 
 For related information, see the topics "Parameter Object", "Parameters Collection", and "PARAMETERS Declaration (SQL)" in DAO Help.
 
@@ -468,7 +468,7 @@ A string containing the name of the desired parameter, for lookup by name. You c
 
 ### Remarks
 
-For a description of the information returned in *`paraminfo`*, see the [`CDaoParameterInfo`](../../mfc/reference/cdaoparameterinfo-structure.md) structure. This structure has members that correspond to the descriptive information under *dwInfoOptions* above.
+For a description of the information returned in *`paraminfo`*, see the [`CDaoParameterInfo`](../../mfc/reference/cdaoparameterinfo-structure.md) structure. This structure has members that correspond to the descriptive information under *`dwInfoOptions`* above.
 
 For related information, see the topic "PARAMETERS Declaration (SQL)" in DAO Help.
 
@@ -549,7 +549,7 @@ The SQL statement that defines the query on which the querydef is based.
 
 ### Remarks
 
-You'll then probably parse the string for keywords, table names, and so on.
+You can parse the string for keywords, table names, and so on.
 
 For related information, see the topics "SQL Property", "Comparison of Microsoft Jet Database Engine SQL and ANSI SQL", and "Querying a Database with SQL in Code" in DAO Help.
 
@@ -610,7 +610,7 @@ Nonzero if the `CDaoQueryDef` object is currently open; otherwise 0.
 
 ### Remarks
 
-A querydef must be in an open state before you use it to call [Execute](#execute) or to create a [CDaoRecordset](../../mfc/reference/cdaorecordset-class.md) object. To put a querydef into an open state call either [Create](#create) (for a new querydef) or [Open](#open) (for an existing querydef).
+A querydef must be in an open state before you use it to call [`Execute`](#execute) or to create a [`CDaoRecordset`](../../mfc/reference/cdaorecordset-class.md) object. To put a querydef into an open state, call either [`Create`](#create) (for a new querydef) or [`Open`](#open) (for an existing querydef).
 
 ## <a name="m_pdatabase"></a> CDaoQueryDef::m_pDatabase
 
@@ -626,7 +626,7 @@ Contains a pointer to the OLE interface for the underlying DAO querydef object.
 
 ### Remarks
 
-This pointer is provided for completeness and consistency with the other classes. However, because MFC rather fully encapsulates DAO querydefs, you are unlikely to need it. If you do use it, do so cautiously. In particular, don't change the value of the pointer unless you know what you're doing.
+This pointer is provided for completeness and consistency with the other classes. However, because MFC rather fully encapsulates DAO querydefs, you're unlikely to need it. If you do use it, do so cautiously. In particular, don't change the value of the pointer unless you know what you're doing.
 
 ## <a name="open"></a> CDaoQueryDef::Open
 
@@ -701,7 +701,7 @@ The number of seconds before a query times out.
 
 ### Remarks
 
-This member function lets you override the default number of seconds before subsequent operations on the connected data source "time out." An operation might time out due to network access problems, excessive query processing time, and so on. Call `SetODBCTimeout` prior to executing a query with this querydef if you want to change the query timeout value. (As ODBC reuses connections, the timeout value is the same for all clients on the same connection.)
+This member function lets you override the default number of seconds before subsequent operations on the connected data source "time out." An operation might time out due to network access problems, excessive query processing time, and so on. Call `SetODBCTimeout` before executing a query with this querydef if you want to change the query timeout value. (As ODBC reuses connections, the timeout value is the same for all clients on the same connection.)
 
 The default value for query timeouts is 60 seconds.
 
@@ -772,9 +772,9 @@ A typical use of `SetSQL` is setting up a querydef object for use in a SQL pass-
 
 ## See also
 
-[CObject Class](../../mfc/reference/cobject-class.md)<br/>
+[`CObject` Class](../../mfc/reference/cobject-class.md)<br/>
 [Hierarchy Chart](../../mfc/hierarchy-chart.md)<br/>
-[CDaoRecordset Class](../../mfc/reference/cdaorecordset-class.md)<br/>
-[CDaoDatabase Class](../../mfc/reference/cdaodatabase-class.md)<br/>
-[CDaoTableDef Class](../../mfc/reference/cdaotabledef-class.md)<br/>
-[CDaoException Class](../../mfc/reference/cdaoexception-class.md)
+[`CDaoRecordset` Class](../../mfc/reference/cdaorecordset-class.md)<br/>
+[`CDaoDatabase` Class](../../mfc/reference/cdaodatabase-class.md)<br/>
+[`CDaoTableDef` Class](../../mfc/reference/cdaotabledef-class.md)<br/>
+[`CDaoException` Class](../../mfc/reference/cdaoexception-class.md)

docs/mfc/reference/cdaoquerydefinfo-structure.md

@@ -10,7 +10,7 @@ helpviewer_keywords: ["DAO (Data Access Objects), QueryDefs collection", "CDaoQu
 The `CDaoQueryDefInfo` structure contains information about a querydef object defined for data access objects (DAO).
 
 > [!NOTE]
-> DAO is supported through Office 2013. DAO 3.6 is the final version, and it's considered obsolete.
+> Data Access Object (DAO) is supported through Office 2013. DAO 3.6 is the final version, and it's considered obsolete.
 
 ## Syntax
 
@@ -35,7 +35,7 @@ struct CDaoQueryDefInfo
 Uniquely names the querydef object. For more information, see the topic "Name Property" in DAO Help. Call [CDaoQueryDef::GetName](../../mfc/reference/cdaoquerydef-class.md#getname) to retrieve this property directly.
 
 *m_nType*<br/>
-A value that indicates the operational type of a querydef object. The value can be one of the following:
+A value that indicates the operational type of a querydef object. The value can be one of:
 
 - `dbQSelect` Select: the query selects records.
 
@@ -87,9 +87,9 @@ The number of seconds the Microsoft Jet database engine waits before a timeout e
 
 ## Remarks
 
-The querydef is an object of class [CDaoQueryDef](../../mfc/reference/cdaoquerydef-class.md). The references to Primary, Secondary, and All above indicate how the information is returned by the [GetQueryDefInfo](../../mfc/reference/cdaodatabase-class.md#getquerydefinfo) member function in class `CDaoDatabase`.
+The querydef is an object of class [CDaoQueryDef](../../mfc/reference/cdaoquerydef-class.md). The references to Primary, Secondary, and All indicate how the information is returned by the [GetQueryDefInfo](../../mfc/reference/cdaodatabase-class.md#getquerydefinfo) member function in class `CDaoDatabase`.
 
-Information retrieved by the [CDaoDatabase::GetQueryDefInfo](../../mfc/reference/cdaodatabase-class.md#getquerydefinfo) member function is stored in a `CDaoQueryDefInfo` structure. Call `GetQueryDefInfo` for the database object in whose QueryDefs collection the querydef object is stored. `CDaoQueryDefInfo` also defines a `Dump` member function in debug builds. You can use `Dump` to dump the contents of a `CDaoQueryDefInfo` object. Class `CDaoDatabase` also supplies member functions for directly accessing all of the properties returned in a `CDaoQueryDefInfo` object, so you'll probably seldom need to call `GetQueryDefInfo`.
+Information retrieved by the [CDaoDatabase::GetQueryDefInfo](../../mfc/reference/cdaodatabase-class.md#getquerydefinfo) member function is stored in a `CDaoQueryDefInfo` structure. Call `GetQueryDefInfo` for the database object in whose QueryDefs collection the querydef object is stored. `CDaoQueryDefInfo` also defines a `Dump` member function in debug builds. You can use `Dump` to dump the contents of a `CDaoQueryDefInfo` object. Class `CDaoDatabase` also supplies member functions for directly accessing all of the properties returned in a `CDaoQueryDefInfo` object, so you'll seldom call `GetQueryDefInfo`.
 
 When you append a new field or parameter object to the Fields or Parameters collection of a querydef object, an exception is thrown if the underlying database doesn't support the data type specified for the new object.
 

docs/mfc/reference/cdaorecordset-class.md

@@ -10,7 +10,7 @@ helpviewer_keywords: ["CDaoRecordset [MFC], CDaoRecordset", "CDaoRecordset [MFC]
 Represents a set of records selected from a data source.
 
 > [!NOTE]
-> DAO is supported through Office 2013. DAO 3.6 is the final version, and it's considered obsolete.
+> Data Access Object (DAO) is supported through Office 2013. DAO 3.6 is the final version, and it's considered obsolete.
 
 
 ## Syntax

docs/mfc/reference/cdaorelationfieldinfo-structure.md

@@ -10,7 +10,7 @@ helpviewer_keywords: ["DAO (Data Access Objects), Relations collection", "CDaoRe
 The `CDaoRelationFieldInfo` structure contains information about a field in a relation defined for data access objects (DAO).
 
 > [!NOTE]
-> DAO is supported through Office 2013. DAO 3.6 is the final version, and it's considered obsolete.
+> Data Access Objects (DAO) is supported through Office 2013. DAO 3.6 is the final version, and it's considered obsolete.
 
 ## Syntax
 
@@ -32,11 +32,11 @@ The name of the field in the foreign table of the relation.
 
 ## Remarks
 
-A DAO relation object specifies the fields in a primary table and the fields in a foreign table that define the relation. The references to Primary in the structure definition above indicate how the information is returned in the `m_pFieldInfos` member of a [CDaoRelationInfo](../../mfc/reference/cdaorelationinfo-structure.md) object obtained by calling the [GetRelationInfo](../../mfc/reference/cdaodatabase-class.md#getrelationinfo) member function of class `CDaoDatabase`.
+A DAO relation object specifies the fields in a primary table and the fields in a foreign table that define the relation. The references to Primary in the structure definition indicate how the information is returned in the `m_pFieldInfos` member of a [CDaoRelationInfo](../../mfc/reference/cdaorelationinfo-structure.md) object obtained by calling the [GetRelationInfo](../../mfc/reference/cdaodatabase-class.md#getrelationinfo) member function of class `CDaoDatabase`.
 
-Relation objects and relation field objects are not represented by an MFC class. Instead, the DAO objects underlying MFC objects of class [CDaoDatabase](../../mfc/reference/cdaodatabase-class.md) contain a collection of relation objects, called the Relations collection. Each relation object, in turn, contains a collection of relation field objects. Each relation field object correlates a field in the primary table with a field in the foreign table. Taken together, the relation field objects define a group of fields in each table, which together define the relation. `CDaoDatabase` lets you access relation objects with a `CDaoRelationInfo` object by calling the `GetRelationInfo` member function. The `CDaoRelationInfo` object, then, has a data member, `m_pFieldInfos`, that points to an array of `CDaoRelationFieldInfo` objects.
+Relation objects and relation field objects aren't represented by an MFC class. Instead, the DAO objects underlying MFC objects of class [CDaoDatabase](../../mfc/reference/cdaodatabase-class.md) contain a collection of relation objects, called the Relations collection. Each relation object, in turn, contains a collection of relation field objects. Each relation field object correlates a field in the primary table with a field in the foreign table. Taken together, the relation field objects define a group of fields in each table, which together define the relation. `CDaoDatabase` lets you access relation objects with a `CDaoRelationInfo` object by calling the `GetRelationInfo` member function. The `CDaoRelationInfo` object has a data member, `m_pFieldInfos`, that points to an array of `CDaoRelationFieldInfo` objects.
 
-Call the [GetRelationInfo](../../mfc/reference/cdaodatabase-class.md#getrelationinfo) member function of the containing `CDaoDatabase` object in whose Relations collection is stored the relation object you are interested in. Then access the `m_pFieldInfos` member of the [CDaoRelationInfo](../../mfc/reference/cdaorelationinfo-structure.md) object. `CDaoRelationFieldInfo` also defines a `Dump` member function in debug builds. You can use `Dump` to dump the contents of a `CDaoRelationFieldInfo` object.
+Call the [GetRelationInfo](../../mfc/reference/cdaodatabase-class.md#getrelationinfo) member function of the containing `CDaoDatabase` object in whose Relations collection is stored the relation object you're interested in. Then access the `m_pFieldInfos` member of the [CDaoRelationInfo](../../mfc/reference/cdaorelationinfo-structure.md) object. `CDaoRelationFieldInfo` also defines a `Dump` member function in debug builds. You can use `Dump` to dump the contents of a `CDaoRelationFieldInfo` object.
 
 ## Requirements