Syntax: Msgbox (Prompt (, Buttons) (, Title) (, Helpfile, Context) )
Syntax: Msgbox (Prompt (, Buttons) (, Title) (, Helpfile, Context) )
Description
prompt
buttons
title
Optional. String expression displayed in the title bar of the dialog box. If
placed in the title bar.
Both optional. These arguments are only applicable when a Help file ha
application.
Value
Description
vbOKOnly
vbOKCancel
vbAbortRetryIgnore
vbYesNoCancel
vbYesNo
vbRetryCancel
Value
Description
vbCritical
16
vbQuestion
32
vbExclamation
48
vbInformation
64
Value
Description
vbDefaultButton1
vbDefaultButton2
256
vbDefaultButton3
512
vbDefaultButton4
768
Fourth Group Determines the modality of the message box. Note generally, you
would not need to use a constant from this group, as you would
want to use the default (application modal). If you specified "system
modal", you would be "hogging" Windows i.e., if a user had
another app open, like Word or Excel, they would not be able to get
back to it until they responded to your app's message box.
Constant
Value
Description
vbApplicationModal
vbSystemModal
4096
There is a fifth group of constants that can be used for the buttons argument which would only be used
under special circumstances:
Constant
Value
Description
vbMsgBoxHelpButton
16384
VbMsgBoxSetForeground
65536
vbMsgBoxRight
524288
vbMsgBoxRtlReading
1048576
When you use MsgBox to with the option to display more than one button (i.e., from the first group,
anything other than "vbOKOnly"), you can test which button the user clicked by comparing the return
value of the Msgbox function with one of these values:
Constant
Value
Description
vbOK
vbCancel
vbAbort
vbRetry
vbIgnore
vbYes
vbNo
Note: To try any of the MsgBox examples, you can simply start a new project, doubleclick on the form, and place the code in the Form_Load event.
There are two basic ways to use MsgBox, depending on whether or not you need to
know which button the user clicked.
If you do NOT need to test which button the user clicked (i.e., you displayed a
message box with only an OK button), then you can use MsgBox as if you were
calling a Sub. You can use the following syntax:
Msgbox arguments
-orCall MsgBox(arguments)
Examples:
o
The statement
MsgBox "Hello there!"
causes the following box to be displayed:
This is the simplest use of MsgBox: it uses only the required prompt argument. Since
the buttons argument was omitted, the default (OK button with no icons)
was used; and since the title argument was omitted, the default title (the
project name) was displayed in the title bar.
o
The statement
MsgBox "The Last Name field must not be blank.", _
vbExclamation, _
"Last Name"
causes the following box to be displayed:
This is how a data entry error might be displayed. Note that vbExclamation was
specified for the buttons argument to specify what icon should be
displayed the fact that we did not add a value from the first group still
causes only the OK button to be displayed. If you wanted to explicitly
indicate that only the OK button should be displayed along with the
exclamation icon, you could have coded the second argument as
vbExclamation + vbOKOnly
making the full statement read:
MsgBox "The Last Name field must not be blank.", _
vbExclamation + vbOKOnly, _
"Last Name"
Remember, for the buttons argument, you can add one value from each of the four
groups.
An alternative (not recommended) is to use the hard-coded number for
the buttons argument, as in:
MsgBox "The Last Name field must not be blank.",
48, "Last Name"
Note also that this example provided a value for the title argument ("Last Name"), which
causes that text to be displayed in the box's title bar.
The format of the MsgBox statement used in this example could also be
used for more critical errors (such as a database problem) by using
the vbCritical icon. You may also want to use the name of the Sub or
Function in which the error occurred for your title argument.
Example:
MsgBox "A bad database error has occurred.", _
vbCritical, _
"UpdateCustomerTable"
Result:
If you DO need to test which button the user clicked (i.e., you displayed a
message box with more than one button), then you must use MsgBox as a
function, using the following syntax:
After the user clicks a button, you would test the return variable (intResponse) for a
value of vbYes or vbNo (6 or 7).
Note that the use of the built-in constants makes the code more readable. The
statement
intResponse = MsgBox("Are you sure you want to
quit?", _
vbYesNo + vbQuestion, _
"Quit")
is more readable than
intResponse = MsgBox("Are you sure you want to
quit?", 36, "Quit")
and
In that you can use a function anywhere a variable can be used, you could use the
MsgBox function directly in an if statement without using a separate variable to
hold the result ("intResponse" in this case). For example, the above example
could have been coded as:
If MsgBox("Are you sure you want to quit?", _
vbYesNo + vbQuestion, _
"Quit")= vbYes Then
End
End If
Note: If desired you could place the code for this example in the cmdExit_Click
event of any of the "Try It" projects.
Following is an example using the vbDefaultButton2 constant:
Dim intResponse As Integer
intResponse = MsgBox("Are you sure you want to
delete all of the rows " _
& "in the Customer table?", _
vbYesNo + vbQuestion + vbDefaultButton2, _
"Delete")
If intResponse = vbYes Then
' delete the rows ...
End If
The message box displayed by this example would look like this:
The sample project for this topic contains a command button for each MsgBox example
given above.