| title | Call Statement (Visual Basic) | |||
|---|---|---|---|---|
| ms.date | 07/20/2015 | |||
| ms.prod | .net | |||
| ms.reviewer | ||||
| ms.suite | ||||
| ms.technology |
|
|||
| ms.topic | article | |||
| f1_keywords |
|
|||
| helpviewer_keywords |
|
|||
| ms.assetid | e5b31571-6867-406f-b8e7-a3f9aae4723a | |||
| caps.latest.revision | 13 | |||
| author | dotnet-bot | |||
| ms.author | dotnetcontent |
Transfers control to a Function, Sub, or dynamic-link library (DLL) procedure.
[ Call ] procedureName [ (argumentList) ]
procedureName
Required. Name of the procedure to call.
argumentList
Optional. List of variables or expressions representing arguments that are passed to the procedure when it is called. Multiple arguments are separated by commas. If you include argumentList, you must enclose it in parentheses.
You can use the Call keyword when you call a procedure. For most procedure calls, you aren’t required to use this keyword.
You typically use the Call keyword when the called expression doesn’t start with an identifier. Use of the Call keyword for other uses isn’t recommended.
If the procedure returns a value, the Call statement discards it.
The following code shows two examples where the Call keyword is necessary to call a procedure. In both examples, the called expression doesn't start with an identifier.
[!code-vbVbVbalrStatements#97]
Function Statement
Sub Statement
Declare Statement
Lambda Expressions