If you noticed in the first answer that was given the user used 'RETURN'
'Return' will work with 'Sub' procedures too, however, it doesn't make sense
in the sample posted in AMercer's reply.
MS online help says:
"Use the Return statement whenever your logic permits it. For more
information, see Return Statement. The compiler can optimize the code better
than if you use Exit Function, Exit Property, or Exit Sub, or allow the End
Function, End Get, End Set, or End Sub statement to generate a return."
On the other hand, MS online help also says:
"A Return statement, returns execution to the expression that invoked the
method. If the method is a subroutine, the statement is equivalent to an Exit
Sub statement and no expression may be supplied."
Conflicting guidance ... what to do. Well, it seemed to me that guidance
about using 'exit xxx' and 'end xxx' was older, and that vb .net gained a
little in performance by functionally equivalent uses of return. So, I've
developed the habit of putting return statements at the bottom of subs. Does
this really not make sense? What does MS say? If there is an advantage, I
want to leave the returns in. If there is a loss or equality, I want to
remove them.