Slight correction:
In VB/VBA, a function DOES automatically return a value if you did not
assign a value to the function within the function. The returned value, in
this case, is the default value of the data type the function is supposed to
return.
For example,
Public Function GetInteger() As Integer
Dim i as Integer
Dim j as Integer
i+j
''Note, no value is assigned to GetInteger
End Function
This function returns 0, which is default value of Integer type
You can even not specify Function's return type, like this:
Public Function GetValue()
'Do something
'You can even not assign a value back to GetValue
End Function
In this case, it return Empty (vbEmpty, since there is VB enum. value to
represent Empty, so we can still say the function returns a value), if you
did not assign any value to the function, or it returns whatever data type
you assign to the function
Sometimes, VB/VBA simply does too much for programmers, that encourages "not
so good practice". My thumb of rule here is to always expiciltly declare a
function's return type and to always assign the function a return value
within the function.
"Ed Jobe" wrote in message
news:5197036@discussion.autodesk.com...
No, vba does not work like lisp. A value is not automatically "returned". In
lisp everything in parens is a function. In vba, to create a "function", you
must assign a value or object to the procedure's name. Otherwise it remains
just a "procedure" that performs some action.
--
----
Ed
----
