Merge pull request #1512 from MicrosoftDocs/main

[admin] merge to live

Author: lindalu-MSFT

Language/Reference/User-Interface-Help/typename-function.md

@@ -44,7 +44,6 @@ The string returned by **TypeName** can be any one of the following:
 |Unknown|An object whose type is unknown|
 |**[Nothing](nothing-keyword.md)**|Object variable that doesn't refer to an object|
 
-<br>
 
 If _varname_ is an [array](../../Glossary/vbe-glossary.md#array), the returned string can be any one of the possible returned strings (or **Variant**) with empty parentheses appended. For example, if _varname_ is an array of integers, **TypeName** returns `"Integer()`".
 
@@ -65,7 +64,6 @@ MyType = TypeName(ArrayVar)    ' Returns "Integer()".
 
 ```
 
-
 ## See also
 
 - [Data types](data-type-summary.md)

access/Concepts/Controls/refer-to-tab-control-objects-in-vba.md

@@ -9,7 +9,7 @@ ms.localizationpriority: medium
 
 # Refer to tab control objects in VBA
 
-Use a tab control to present several pages of information about a single form. A tab control is useful when your form contains information that can be sorted into two or more categories. 
+Use a tab control to present several pages of information about a single form. A tab control is useful when your form contains information that can be sorted into two or more categories.
 
 In most ways, a tab control works like other controls on a form and can be referred to as a member of a form's **[Controls](../../../api/Access.Controls.md)** collection. For example, to refer to a tab control named TabControl1 on a form named Form1, you can use the following expression:
 
@@ -25,10 +25,9 @@ Form1!TabControl1
 
 ```
 
-
 ## Refer to the Pages collection
 
-A tab control contains one or more pages. Each page in a tab control is referenced as a member of the tab control's **[Pages](../../../api/Access.TabControl.Pages.md)** collection. Each page in the **Pages** collection can be referred to by either its **[PageIndex](../../../api/Access.Page.PageIndex.md)** property setting (which reflects the page's position in the collection starting with 0), or by the page's **[Name](../../../api/Access.Page.Name.md)** property setting. 
+A tab control contains one or more pages. Each page in a tab control is referenced as a member of the tab control's **[Pages](../../../api/Access.TabControl.Pages.md)** collection. Each page in the **Pages** collection can be referred to by either its **[PageIndex](../../../api/Access.Page.PageIndex.md)** property setting (which reflects the page's position in the collection starting with 0), or by the page's **[Name](../../../api/Access.Page.Name.md)** property setting.
 
 There is no default collection for the **[TabControl](../../../api/Access.TabControl.md)** object, so when referring to items in the **Pages** collection by their index value, or to properties of the **Pages** collection, you must explicitly refer to the **Pages** collection.
 
@@ -46,7 +45,7 @@ Page1.Caption = "First Page"
 
 ```
 
-> [!NOTE] 
+> [!NOTE]
 > If a user or code changes a page's **PageIndex** property, the reference to the page's index and the page's position in the page order change. In this case, if you want to maintain an absolute reference to a page, refer to the page's **Name** property.
 
 The **Pages** collection has one property, **[Count](../../../api/Access.Pages.Count.md)**, that returns the number of pages in a tab control. Note that this property is not a property of the tab control itself, but of its **Pages** collection, so you must explicitly refer to the collection. For example, to determine the number of pages in TabControl1, use the following statement:
@@ -56,7 +55,6 @@ TabControl1.Pages.Count
 
 ```
 
-
 ## Refer to and change the current page
 
 A tab control's default property is **[Value](../../../api/Access.TabControl.Value.md)**, which returns an integer that identifies the current page: 0 for the first page, 1 for the second page, and so on. The **Value** property is available only in VBA code or in expressions. By reading the **Value** property at run time, you can determine which page is currently on top. For example, the following statement returns the value for the current page of TabControl1:
@@ -66,7 +64,7 @@ TabControl1.Value
 
 ```
 
-> [!NOTE] 
+> [!NOTE]
 > Because the **Value** property is the default property for a tab control, you don't have to refer to it explicitly. For this reason, you could omit `.Value` from the preceding example.
 
 Setting a tab control's **Value** property at run time changes the focus to the specified page, making it the current page. For example, the following statement moves the focus to the third page of TabControl1:
@@ -94,10 +92,9 @@ Page1.PageIndex = 1
 
 The **PageIndex** property is more typically set at design time in a page's property sheet. You can also set the page order by right-clicking the border of a tab control, and then clicking **Page Order** on the shortcut menu.
 
-
 ## Refer to controls on a tab control page
 
-The controls you place on a tab control page are part of the same collection as all controls on the form. For this reason, each control on a tab control page must have a name that is unique with respect to all other controls on the same form. Refer to controls on a tab control page by using the same syntax for controls on a form without a tab control. 
+The controls you place on a tab control page are part of the same collection as all controls on the form. For this reason, each control on a tab control page must have a name that is unique with respect to all other controls on the same form. Refer to controls on a tab control page by using the same syntax for controls on a form without a tab control.
 
 ```vb
 Forms!Employees!HomePhone 
@@ -132,11 +129,8 @@ ErrorHandler:
 End Sub
 ```
 
-<br/>
-
 Additionally, each page on a tab control has its own **Controls** collection. By using a page's **Controls** collection, you can refer to controls on each page. The following code enumerates the controls for each page of the tab control on the Employees form.
 
-
 ```vb
 Sub ListPageControls() 
 

access/Concepts/Data-Access-Objects/set-properties-of-data-access-objects-in-visual-basic.md

@@ -22,7 +22,6 @@ Most of the properties you can set for DAO objects are DAO properties. These pro
 
 To set a property that's defined by the Access database engine, refer to the object in the DAO hierarchy. The easiest and fastest way to do this is to create object variables that represent the different objects you need to work with, and refer to the object variables in subsequent steps in your code. For example, the following code creates a new **TableDef** object and sets its **Name** property:
 
-
 ```vb
 Dim dbs As DAO.Database 
 Dim tdf As DAO.TableDef 
@@ -31,7 +30,6 @@ Set tdf = dbs.CreateTableDef
 tdf.Name = "Contacts"
 ```
 
-
 ## Set Microsoft Access properties for DAO objects
 
 When you set a property that's defined by Microsoft Access, but applies to a DAO object, the Access database engine doesn't automatically recognize the property as a valid property. The first time you set the property, you must create the property and append it to the **Properties** collection of the object to which it applies. Once the property is in the **Properties** collection, it can be set in the same manner as any DAO property.
@@ -48,8 +46,6 @@ Keep in mind that when you create the property, you must correctly specify its *
 |**True** / **False**|**dbBoolean**|
 |An integer|**dbInteger**|
 
-<br/>
-
 The following table lists some Microsoft Access-defined properties that apply to DAO objects.
 
 |**DAO object**|**Microsoft Access-defined properties**|

access/Concepts/Miscellaneous/0-database-engine-driver.md

@@ -10,7 +10,7 @@ ms.date: 06/08/2019
 ms.localizationpriority: medium
 ---
 
-# 0 Database Engine driver 
+# 0 Database Engine driver
 
 **Applies to:** Access 2013 | Access 2016
 
@@ -19,13 +19,15 @@ When you install the Microsoft Access database engine database driver, the Setup
 ## Microsoft Jet Engine initialization settings
 
 The **Access Connectivity Engine\Engines** folder includes initialization settings for the msjet40.dll database engine, used for access to Microsoft Access databases. Typical initialization settings for the entries in this folder are shown in the following example.
+
 ```jet
     SystemDB = <path>\System.mdb
 
     CompactBYPkey = 1
 
     PrevFormatCompactWithUNICODECompression=1
 ```
+
 The Microsoft Access database engine uses the following entries.
 
 |**Entry**|**Description**|
@@ -35,6 +37,7 @@ The Microsoft Access database engine uses the following entries.
 |PrevFormatCompactWithUNICODECompression|Microsoft Access database engine databases use the Unicode character set to store textual data. Compressing the Unicode data can significantly improve the performance of the database because of the reduced number of page read/write operations that are needed afterwards. This key determines if databases created by the Microsoft Jet database engine version 3.x or earlier should be created with compressed Unicode or un-compressed Unicode.<br/><br/>**NOTE** This setting does not apply to compacting Microsoft Access database engine databases. Microsoft Access database engine databases will default to keep the compression settings with which they were created.|
 
 The **Access Connectivity Engine\Engines\ACE** folder includes initialization settings for the Ace.dll database engine, used for access to Microsoft Access databases. Typical initialization settings for the entries in this folder are shown in the following example.
+
 ```jet
 
     FlushTransactionTimeout=500
@@ -63,11 +66,9 @@ The **Access Connectivity Engine\Engines\ACE** folder includes initialization se
 
     PagesLockedToTableLock=0
 
-<br/>
 
 The Microsoft Access database engine uses the following entries.
 
-<br/>
 ```
 
 |Entry|Description|
@@ -86,10 +87,10 @@ The Microsoft Access database engine uses the following entries.
 |SharedAsyncDelay|Specifies the length of time, in milliseconds, to defer an asynchronous flush of a shared database. The default value is 0. Values are of type REG_DWORD.|
 |PagesLockedToTableLock|During bulk operations it is often more efficient to lock a whole table, instead of obtaining locks for each individual page of the table as you try to access it. This setting specifies the number of pages that the Microsoft Access database engine will allow to be locked in any particular transaction before the Access database engine attempts to escalate to an exclusive table lock The default value of 0 indicates that the Access database engine will never automatically change from page locking to table locking.|
 
-> [!NOTE] 
+> [!NOTE]
 > This setting should be used carefully. If a database is needed for multi-user access, locking a whole table could cause locking conflicts for other users. This would be especially severe if a small number was used for this setting. Even when a larger number was used, such as 25 or 50, the operation for other users might become unpredictable.
 
-> [!NOTE] 
+> [!NOTE]
 > When you change Windows Registry settings, you must exit and then restart the database engine for the new settings to take effect.
 
 ## See also

access/Concepts/Miscellaneous/calculating-fields-in-sql-functions.md

@@ -27,8 +27,6 @@ The following table provides examples of calculations on fields from the Orders
 
 The following example calculates the average discount amount of all orders in the Northwind.mdb database. It multiplies the values in the UnitPrice and Discount fields to determine the discount amount of each order and then calculates the average. Use this expression in an SQL statement in Visual Basic code:
 
-<br/>
-
 ```sql
 SELECT Avg(UnitPrice * Discount) AS [Average Discount] FROM [Order Details];
 ```

access/Concepts/Miscellaneous/collections-ado-for-visual-c-plus-plus-syntax.md

@@ -15,23 +15,23 @@ ms.localizationpriority: medium
 
 ### Methods
 
-[Append](https://msdn.microsoft.com/library/cca133af-2b95-877d-0488-0d99631623f2%28Office.15%29.aspx)(IDispatch * _Object_ ) 
+[Append](https://msdn.microsoft.com/library/cca133af-2b95-877d-0488-0d99631623f2%28Office.15%29.aspx)(IDispatch * _Object_ )
 
-[Delete](https://msdn.microsoft.com/library/03ffc24d-fea2-30fa-c8e9-43eb524fd51f%28Office.15%29.aspx)(VARIANT  _Index_ ) 
+[Delete](https://msdn.microsoft.com/library/03ffc24d-fea2-30fa-c8e9-43eb524fd51f%28Office.15%29.aspx)(VARIANT  _Index_ )
 
 [Refresh](https://msdn.microsoft.com/library/f1c8829f-9c7d-12b6-7470-727ff38d663e%28Office.15%29.aspx)(void)
 
 ### Properties
 
 [get_Count](https://msdn.microsoft.com/library/b59f9581-ffd1-471d-44fa-3c1bb812e140%28Office.15%29.aspx)(long * _c_ )
 
-[get_Item](https://msdn.microsoft.com/library/793c305f-0e5b-a529-e21f-b7ab0843ed49%28Office.15%29.aspx)(VARIANT  _Index,_ _ADOParameter ** _ppvObject_ )
+[get_Item](https://msdn.microsoft.com/library/793c305f-0e5b-a529-e21f-b7ab0843ed49%28Office.15%29.aspx)(VARIANT  _Index,_ ADOParameter ** _ppvObject_ )
 
 ## Fields
 
 ### Methods
 
-[Append](https://msdn.microsoft.com/library/cca133af-2b95-877d-0488-0d99631623f2%28Office.15%29.aspx)(BSTR  _bstrName,_ DataTypeEnum _Type,_ long _DefinedSize,_ FieldAttributeEnum _Attrib_ ) 
+[Append](https://msdn.microsoft.com/library/cca133af-2b95-877d-0488-0d99631623f2%28Office.15%29.aspx)(BSTR  _bstrName,_ DataTypeEnum _Type,_ long _DefinedSize,_ FieldAttributeEnum _Attrib_ )
 
 [Delete](https://msdn.microsoft.com/library/adc66365-703f-4491-fc5b-dbc9bca2ac53%28Office.15%29.aspx)(VARIANT  _Index_ )
 
@@ -43,7 +43,6 @@ ms.localizationpriority: medium
 
 [get_Item](https://msdn.microsoft.com/library/793c305f-0e5b-a529-e21f-b7ab0843ed49%28Office.15%29.aspx)(VARIANT  _Index,_ ADOField ** _ppvObject_ )
 
-
 ## Errors
 
 ### Methods
@@ -58,7 +57,6 @@ ms.localizationpriority: medium
 
 [get_Item](https://msdn.microsoft.com/library/793c305f-0e5b-a529-e21f-b7ab0843ed49%28Office.15%29.aspx)(VARIANT  _Index,_ ADOError ** _ppvObject_ )
 
-
 ## Properties
 
 ### Methods
@@ -80,4 +78,4 @@ ms.localizationpriority: medium
 - [Access developer and VBA programming help center (FMS)](https://www.fmsinc.com/MicrosoftAccess/developer/)
 - [Access posts on StackOverflow](https://stackoverflow.com/questions/tagged/ms-access)
 
-[!include[Support and feedback](~/includes/feedback-boilerplate.md)]
+[!include[Support and feedback](~/includes/feedback-boilerplate.md)]

access/Concepts/Miscellaneous/create-a-database-template-programmatically.md

@@ -12,7 +12,6 @@ ms.localizationpriority: medium
 
 The **SaveAsTemplate** method enables you to convert an existing Access database file to a database template (.accdt) format file that can be featured on the **Getting Started with Microsoft Office Access** page.
 
-
 ## Syntax
 
 _expression_. **SaveAsTemplate**(**_TemplateLocation_**, **_TemplateName_**, **_PreviewImage_**, **_Description_**, **_Category_**, **_Keywords_**, **_Identifier_**, **_Reserved_**)
@@ -21,8 +20,6 @@ _expression_ A variable that represents a **TemplateCreator** object.
 
 The following table describes the arguments of the **SaveAsTemplate** method.
 
-<br/>
-
 |Name|Required/Optional|Data type|Description|
 |:-----|:-----|:-----|:-----|
 | _TemplateLocation_|Required|**String**|The full path and file name of the database template to create.For the template to appear on the **Getting Started with Microsoft Office Access** page, it must be saved to **Microsoft\Templates** subfolder of the user's Application Data folder.<br/><br/>In Windows XP, the default location of the Application Data folder is **C:\Documents and Settings\ _User Name_ \Application Data**, where _User Name_ is the name of the user who is currently logged on.<br/><br/>In Windows Vista, the default location of the Application Data folder is **C:\Users\ _User Name_ \AppData\Roaming**, where _User Name_ is the name of the user who is currently logged on. Use the **Environ** function to determine the current location of the user's Application Data folder. The following code illustrates how to do this. `strTemplateLocation = Environ("AppData") & "\Microsoft\Templates\"`|

access/Concepts/Miscellaneous/create-a-deployment-package-programmatically.md

@@ -12,7 +12,6 @@ ms.localizationpriority: medium
 
 The **CreateInstallPackage** method enables you to create a deployment package programmatically.
 
-
 ## Syntax
 
 _expression_. **CreateInstallPackage**(**_WizardSettingsFile_**)
@@ -21,8 +20,6 @@ _expression_ A variable that represents an **AccessDeveloperExtensions** object.
 
 The following table describes the arguments of the **CreateInstallPackage** method.
 
-<br/>
-
 |Name|Required/Optional|Data type|Description|
 |:-----|:-----|:-----|:-----|
 | _WizardSettingsFile_|Required|**String**|The path and file name of the wizard template file that contains the settings to use when creating the deployment package. To create a wizard template (.adepsws), click **Save Wizard Settings** on any Package Solution Wizard page.|
@@ -65,7 +62,6 @@ End Sub
 To use this example, you must set a reference to the Access Developer Extensions type library. To do this, follow these steps:
 
 1. On the **Tools** menu, click **References**.
-    
 2. Select the **Microsoft Office Access Developer Extensions Type Library 1.0** check box, and then click **OK**.
 
 [!include[Support and feedback](~/includes/feedback-boilerplate.md)]

access/Concepts/Miscellaneous/create-a-shortcut-menu-for-a-form-form-control-or-report.md

@@ -3,7 +3,7 @@ title: Create a shortcut menu for a form, form control, or report
 ms.prod: access
 ms.assetid: 56fe8923-053f-e04d-78d6-c4dd814b6499
 ROBOTS: INDEX
-ms.date: 06/08/2019
+ms.date: 02/20/2022
 ms.localizationpriority: medium
 ---
 
@@ -20,7 +20,7 @@ To create a shortcut menu, you first have to create a **[CommandBar](../../../ap
 
 The following example creates a shortcut menu named **SimpleShortcutMenu** that contains two commands, **Remove Filter/Sort** and **Filter by Selection**.
 
-> [!NOTE] 
+> [!NOTE]
 > To use the following examples, you must set a reference to the **Microsoft Office 15.0 Object Library**. See [Set References to Type Libraries](../Settings/set-references-to-type-libraries.md) for more information about how to set references.
 
 ```vb
@@ -81,8 +81,6 @@ Set cmbRightClick = Nothing
 End Sub
 ```
 
-<br/>
-
 The following example creates a shortcut menu named **cmdReportRightClick** that contains commands that are useful to use with a report. This example shows how to change the **Caption** property of each control as they're added to the shortcut menu.
 
 ```vb
@@ -135,8 +133,6 @@ Sub CreateReportShortcutMenu()
 End Sub
 ```
 
-<a name="AboutContributors"> </a>
-
 ## About the contributors
 
 Sample code provided by Edwin Blancovitch, president of [Advanced Developers.net](https://advdev.net/), creators of [Easy Payroll](https://www.easypayroll.net/), a software package to manage your human resources, payroll, scheduling, time, and attendance needs.

access/Concepts/Miscellaneous/invalid-sql-syntaxexpected-constraint-nameerror-3721.md

@@ -17,8 +17,6 @@ When defining referential integrity from a SQL DDL statement, it is necessary to
 CREATE TABLE Customers (CLstNm TEXT(50), CFrstNm TEXT(25), CONSTRAINT PRIMARY KEY (CFrstNm, CLstNm));
 ```
 
-<br/>
-
 To prevent the error, include a name after the CONSTRAINT keyword:
 
 ```sql

access/Concepts/Miscellaneous/new-in-access-for-developers.md

@@ -2,7 +2,7 @@
 title: New in Access for developers
 ms.prod: access
 ms.assetid: df778f51-d65e-4c30-b618-65003ceb39b3
-ms.date: 08/06/2021
+ms.date: 02/06/2022
 ms.localizationpriority: medium
 ---
 
@@ -30,7 +30,7 @@ An Access 2013 app is online the moment it's created. You can decide to share th
 
 ## Views
 
-Views (known as  _"forms"_ in Access desktop databases) provide the means by which users will interact with your Access app. Views in Access 2013 apps contain a common set of user interface elements that enable rapid creation of new apps.
+Views (known as _"forms"_ in Access desktop databases) provide the means by which users will interact with your Access app. Views in Access 2013 apps contain a common set of user interface elements that enable rapid creation of new apps.
 
 Access 2013 is designed to enable you to create functional views with little intervention. When you create a new table, Access automatically creates two views. The following figure shows a new table with the automatically-created views.