Merge branch 'master' of https://github.com/MicrosoftDocs/VBA-Docs

Author: Jiayue Hu (Beyondsoft Consulting Inc)

Language-Reference/Concepts/Getting-Started/64-bit-visual-basic-for-applications-overview.md

@@ -83,7 +83,7 @@ To write code that can port between both 32-bit and 64-bit versions of Office yo
 To write code that can work in both new and older versions of Office you can use a combination of the new  **VBA7** and **Win64** conditional[Compiler Constants](compiler-constants.md). The  **Vba7** conditional compiler constant is used to determine if code is running in version 7 of the VB editor (the VBA version that ships in Office 2010). The **Win64** conditional compilation constant is used to determine which version (32-bit or 64-bit) of Office is running.
 
 
-```
+```vb
 #if Vba7 then 
 '  Code is running in the new VBA7 editor 
      #if Win64 then 

Language-Reference/Concepts/Getting-Started/avoiding-naming-conflicts.md

@@ -28,7 +28,7 @@ Most naming conflicts can be resolved by preceding each identifier with a qualif
 
 
 
-```
+```vb
 YourProject.YourModule.YourSub MyProject.MyModule.MyVar
 ```
 

Language-Reference/Concepts/Getting-Started/calling-sub-and-function-procedures.md

@@ -98,7 +98,7 @@ The following example calls the  **MsgBox** function using named arguments. The
 
 
 
-```
+```vb
 answer3 = MsgBox(Title:="Question 3", _ 
 Prompt:="Are you happy with your salary?", Buttons:=4) 
 

Language-Reference/Concepts/Getting-Started/creating-object-variables.md

@@ -84,7 +84,7 @@ Setting an object variable equal to  **Nothing** discontinues the association of
 
 
 
-```
+```vb
 If Not MyObject Is Nothing Then 
  ' Variable refers to valid object. 
  . . . 
@@ -111,7 +111,7 @@ You can call the procedure and pass the current instance of the object as an arg
 
 
 
-```
+```vb
 ChangeObjectColor Me 
 
 ```

Language-Reference/Concepts/Getting-Started/executing-code-when-setting-properties.md

@@ -17,7 +17,7 @@ The  **Property Let** statement allows you to create a procedure that sets the v
 
 
 
-```
+```vb
 Form1.Inverted = True 
 
 ```
@@ -46,7 +46,7 @@ This  **Property Get** procedure is used to return the current state of the prop
 
 
 
-```
+```vb
 Property Get Inverted() As Boolean 
  Inverted = IsInverted 
 End Property 

Language-Reference/Concepts/Getting-Started/understanding-automation.md

@@ -17,7 +17,7 @@ When an application supports Automation, the objects the application exposes can
 
 
 
-```
+```vb
 MyObj.Insert "Hello, world." ' Place text. 
 MyObj.Bold = True ' Format text. 
 If Mac = True ' Check your platform constant 

Language-Reference/Concepts/Getting-Started/using-data-types-efficiently.md

@@ -38,7 +38,7 @@ This statement declares that a variable  `X` is an integer — a whole number be
 
 
 
-```
+```vb
 X = 32768        ' Causes error. 
 X = 5.9        ' Sets x to 6. 
 

Language-Reference/Concepts/Getting-Started/using-parentheses-in-code.md

@@ -14,7 +14,7 @@ ms.date: 06/08/2017
  **Sub** procedures, built-in[statements](vbe-glossary.md), and some [methods](vbe-glossary.md) don't return a value, so the[arguments](vbe-glossary.md) aren't enclosed in parentheses. For example:
 
 
-```
+```vb
 MySub "stringArgument", integerArgument 
 
 ```
@@ -34,7 +34,7 @@ To use the return value of a function, enclose the arguments in parentheses, as
 
 
 
-```
+```vb
 Answer3 = MsgBox("Are you happy with your salary?", 4, "Question 3") 
 
 ```
@@ -53,7 +53,7 @@ The following example calls the  **MsgBox** function using named arguments and a
 
 
 
-```
+```vb
 answer3 = MsgBox(Title:="Question 3", _ 
  Prompt:="Are you happy with your salary?", Buttons:=4) 
 

Language-Reference/Concepts/Getting-Started/writing-a-property-procedure.md

@@ -48,7 +48,7 @@ A  **Property Get** procedure declaration takes one less argument than the relat
 
 
 
-```
+```vb
 Property Let Names(intX As Integer, intY As Integer, varZ As Variant) 
  ' Statement here. 
 End Property 

Language-Reference/Concepts/Getting-Started/writing-assignment-statements.md

@@ -28,7 +28,7 @@ The  **Let** statement is optional and is usually omitted. For example, the prec
 
 
 
-```
+```vb
 Let yourName = InputBox("What is your name?"). 
 
 ```

Language-Reference/Concepts/Getting-Started/writing-declaration-statements.md

@@ -32,9 +32,6 @@ The  **Dim** statement declares the `myCell` variable. The data type is an objec
 ## See also
 
 
-#### Concepts
-
-
 [Writing a Sub Procedure](writing-a-sub-procedure.md)
 [Declaring Constants](declaring-constants.md)
 [Declaring Variables](declaring-variables.md)

Language-Reference/Glossary/vbe-glossary.md

@@ -502,7 +502,7 @@ By assigning values to named arguments, you can use the following statement:
 
 
 
-```
+```vb
 DoSomeThing namedarg3 := 4, namedarg2 := 5, namedarg1 := 20 
 
 ```

Language-Reference/Language-Reference/User-Interface-Help/a-procedure-with-a-paramarray-argument-cannot-be-called-with-named-arguments.md

@@ -20,7 +20,7 @@ All [arguments](vbe-glossary.md) in a call to a[procedure](vbe-glossary.md) defi
 
 
 
-  ```
+  ```vb
   MySub Arg1, Arg2, 7,, 44,,,3 
   ```
 

Language-Reference/Language-Reference/User-Interface-Help/add-method-microsoft-forms.md

@@ -57,7 +57,7 @@ The following syntax will return the  **Text** property of the specified control
 
 
 
-```
+```vb
 userform1.thebox.text
 
 ```
@@ -66,7 +66,7 @@ If you add a control at run time, you must use the exclamation syntax to referen
 
 
 
-```
+```vb
 userform1!thebox.text
 
 

Language-Reference/Language-Reference/User-Interface-Help/array-already-dimensioned.md

@@ -23,7 +23,7 @@ Dim MyArray()
   ```
 
 
-  ```
+  ```vb
   ReDim MyArray(n) 
 
   ```

Language-Reference/Language-Reference/User-Interface-Help/bad-file-name-or-number-error-52.md

@@ -28,7 +28,7 @@ An error occurred trying to access the specified file. This error has the follow
 
 - There is an invalid name or number.
 
-  ```
+  ```vb
   LETTER.DOC 
 My Memo.Txt 
 BUDGET.92 

Language-Reference/Language-Reference/User-Interface-Help/bad-record-length-error-59.md

@@ -17,7 +17,7 @@ The length of a record [variable](vbe-glossary.md) in a **Get** or **Put** state
 
 - The record variable's length differs from the length specified in the corresponding  **Open** statement. Make sure the sum of the sizes of fixed-length[variables](vbe-glossary.md) in the[user-defined type](vbe-glossary.md) defining the record variable's type is the same as the value stated in the **Open** statement's **Len** clause. In the following example, assume `RecVar` is a variable of the appropriate type. You can use the **Len** function to specify the length, as follows:
 
-  ```
+  ```vb
   Open MyFile As #1 Len = Len(RecVar) 
 
   ```

Language-Reference/Language-Reference/User-Interface-Help/calendar-property.md

@@ -29,7 +29,7 @@ You can only set the  **Calendar** property programmatically. For example, to us
 
 
 
-```
+```vb
 Calendar = vbCalHijri
 
 

Language-Reference/Language-Reference/User-Interface-Help/call-statement.md

@@ -22,7 +22,7 @@ The  **Call** statement syntax has these parts:
 
 |**Part**|**Description**|
 |:-----|:-----|
-|**Call**|Optional; [keyword](vbe-glossary.md). If specified, you must enclose  _argumentlist_ in parentheses. For example:<p>```Call MyProc(0)```</p>|
+|**Call**|Optional; [keyword](vbe-glossary.md). If specified, you must enclose  _argumentlist_ in parentheses. For example:<p>```vbCall MyProc(0)```</p>|
 | _name_|Required. Name of the procedure to call.|
 | _argumentlist_|Optional. Comma-delimited list of [variables](vbe-glossary.md), [arrays](vbe-glossary.md), or [expressions](vbe-glossary.md) to pass to the procedure. Components of _argumentlist_ may include the keywords **ByVal** or **ByRef** to describe how the[arguments](vbe-glossary.md) are treated by the called procedure. However, **ByVal** and **ByRef** can be used with **Call** only when calling a DLL procedure. On the Macintosh, **ByVal** and **ByRef** can be used with **Call** when making a call to a Macintosh code resource.|
 

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

@@ -32,7 +32,7 @@ In the following example, the first line uses  **CallByName** to set the **Mouse
 
 
 
-```
+```vb
 CallByName Text1, "MousePointer", vbLet, vbCrosshair
 Result = CallByName (Text1, "MousePointer", vbGet)
 CallByName Text1, "Move", vbMethod, 100, 100

Language-Reference/Language-Reference/User-Interface-Help/can-t-assign-to-an-array.md

@@ -28,7 +28,7 @@ Each element of an [array](vbe-glossary.md) must have its value assigned individ
 
 
 
-  ```
+  ```vb
   Arr1 = Arr2    ' Invalid assignment. 
 Arr1() = Arr2()    ' Invalid assignment. 
 
@@ -51,7 +51,7 @@ MyVar = Arr2()
 
 
 
-  ```
+  ```vb
   MyVar(3) = MyVar(1) + MyVar(5) 
   ```
 

Language-Reference/Language-Reference/User-Interface-Help/chdir-statement.md

@@ -26,7 +26,7 @@ The required  _path_ [argument](vbe-glossary.md) is a [string expression](vbe-gl
 The  **ChDir** statement changes the default directory or folder but does not change the default drive. A different statement, **[ChDrive](chdrive-statement.md)**, changes the default drive. 
 
 
-```
+```vb
 ChDir "D:\TMP" ' Make "D:\TMP" the current folder. 
 
 ChDrive "D"    ' Make "D" the current drive. 
@@ -37,7 +37,7 @@ ChDrive "D"    ' Make "D" the current drive.
 On the Power Macintosh, the default drive always changes to the drive specified in  _path_. Full path specifications begin with the volume name, and relative paths begin with a colon ( **:** ). **ChDir** resolves any aliases specified in the path:
 
 
-```
+```vb
 ChDir "MacDrive:Tmp" ' On the Macintosh. 
 
 ```
@@ -46,7 +46,7 @@ ChDir "MacDrive:Tmp" ' On the Macintosh.
 Note that when making relative directory changes, different symbols are used in Microsoft Windows and on the Macintosh:
 
 
-```
+```vb
 ChDir ".." ' Moves up one directory in Microsoft Windows. 
 ChDir "::" ' Moves up one directory on the Macintosh.
 ```
@@ -59,7 +59,7 @@ On the Macintosh, the default drive name is "HD" and portions of the pathname ar
 
 This example uses the  **ChDir** statement to change the current directory or folder. If the default drive is C, then default drive remains C, even though the default folder changes to a folder on drive D:
 
-```
+```vb
 ' Assume "C:" is the current drive. The following statement changes 
 ' the default directory on drive "D:". "C:" remains the current drive. 
 ChDir "D:\WINDOWS\SYSTEM" 

Language-Reference/Language-Reference/User-Interface-Help/chdrive-statement.md

@@ -25,7 +25,7 @@ On the Macintosh,  **ChDrive** changes the current folder to the root folder of
 This example uses the  **ChDrive** statement to change the current drive. On the Macintosh, "HD:" is the default drive name and **ChDrive** would change the current folder to the root folder of the specified drive. The following example assumes the machine actually has a drive named D.
 
 
-```
+```vb
 ChDrive "D" ' Make "D" the current drive. 
 
 ```

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

@@ -21,15 +21,15 @@ When Visual Basic is launched from the command line, any portion of the command
 
 
 
-```text
+```vbtext
 VB /cmd cmdlineargs
 ```
 
 For applications developed with Visual Basic and compiled to an .exe file,  **Command** returns any arguments that appear after the name of the application on the command line. For example:
 
 
 
-```text
+```vbtext
 MyApp cmdlineargs
 ```
 

Language-Reference/Language-Reference/User-Interface-Help/const-directive.md

@@ -35,7 +35,7 @@ Conditional compiler constants are always evaluated at the [module level](vbe-gl
 This example uses the  **#Const** directive to declare conditional compiler constants for use in **#If...#Else...#End If** constructs.
 
 
-```
+```vb
 #Const DebugVersion = 1 ' Will evaluate true in #If block. 
 
 ```

Language-Reference/Language-Reference/User-Interface-Help/copyfolder-method.md

@@ -34,7 +34,7 @@ Wildcard characters can only be used in the last path component of the  _source_
 
 
 
-```
+```vb
 FileSystemObject.CopyFolder "c:\mydocuments\letters\*", "c:\tempfolder\"
 
 ```
@@ -43,7 +43,7 @@ But you can't use:
 
 
 
-```
+```vb
 FileSystemObject.CopyFolder "c:\mydocuments\*\*", "c:\tempfolder\"
 
 

Language-Reference/Language-Reference/User-Interface-Help/createeventproc-method-vba-add-in-object-model.md

@@ -30,7 +30,7 @@ Use the  **CreateEventProc** method to create an event procedure. For example, t
 
 
 
-```
+```vb
 TextLocation = CM.CreateEventProc("Click", "Command1")
 ```
 

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

@@ -81,7 +81,7 @@ You can pass an object returned by the  **CreateObject** function to a function
 
 
 
-```
+```vb
 Call MySub (CreateObject("Excel.Application"))
 ```
 

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

@@ -52,7 +52,7 @@ The  **DateAdd** function won't return an invalid date. The following example ad
 
 
 
-```
+```vb
 DateAdd("m", 1, "31-Jan-95")
 
 ```

Language-Reference/Language-Reference/User-Interface-Help/debugging-tab-project-properties-dialog-box.md

@@ -37,7 +37,7 @@ Selecting a startup component on the Debugging tab does not affect the Startup O
 
 
 
-```text
+```vbtext
 Startup Object=Sub Main 
 ```
 
@@ -46,7 +46,7 @@ and
 
 
 
-```text
+```vbtext
 Start Component=DHTMLPage1 
 ```
 

Language-Reference/Language-Reference/User-Interface-Help/description-property-visual-basic-for-applications.md

@@ -23,7 +23,7 @@ The  **Description** property setting consists of a short description of the err
 This example assigns a user-defined message to the  **Description** property of the **Err** object.
 
 
-```
+```vb
 Err. Description = "It was not possible to access an object necessary " _
 &; "for this operation."