Skip to content

Latest commit

 

History

History
37 lines (28 loc) · 2.27 KB

how-to-call-a-procedure-that-does-not-return-a-value.md

File metadata and controls

37 lines (28 loc) · 2.27 KB
Raw
description title ms.date helpviewer_keywords ms.assetid
Learn more about: How to: Call a Procedure that Does Not Return a Value (Visual Basic)
How to: Call a Procedure that Does Not Return a Value
07/20/2015
procedure calls [Visual Basic], returning values
Visual Basic code, procedures
procedures [Visual Basic], calling
259b49a3-a3c1-4254-ba8c-73cdc4127703

How to: Call a Procedure that Does Not Return a Value (Visual Basic)

A Sub procedure does not return a value to the calling code. You call it explicitly with a stand-alone calling statement. You cannot call it by simply using its name within an expression.

To call a Sub procedure

  1. Specify the name of the Sub procedure.

  2. Follow the procedure name with parentheses to enclose the argument list. If there are no arguments, you can optionally omit the parentheses. However, using the parentheses makes your code easier to read.

  3. Place the arguments in the argument list within the parentheses, separated by commas. Be sure you supply the arguments in the same order that the Sub procedure defines the corresponding parameters.

    The following example calls the Visual Basic xref:Microsoft.VisualBasic.Interaction.AppActivate%2A function to activate an application window. xref:Microsoft.VisualBasic.Interaction.AppActivate%2A takes the window title as its sole argument. It does not return a value to the calling code. If a Notepad process is not running, the example throws an xref:System.ArgumentException. The Shell procedure assumes the applications are in the paths specified.

    [!code-vbVbVbalrCatRef#11]

See also