Subs vs. Functions Returning Values By Reference in Ribbon Callbacks To return a value from a ribbon callback, you need to pass the value back to the calling procedure using an argument that has been passed by reference.
Subs vs. Functions Every Function in VBA Returns a Value Whether you assign one explicitly or not, every function in VBA has a return value.
Subs vs. Functions Returning Multiple Values from a Function in VBA Using a UDT You can return multiple values from a VBA procedure by using a simple User Defined Type (UDT). Though, some situations require a "complex" UDT.
Subs vs. Functions Using ByRef to Return Multiple Values from a Sub (or Function) You can "return" multiple values from a VBA procedure by passing your arguments by reference.
Subs vs. Functions Calling VBA Functions from the Form or Report Property Sheet There are two basic ways to handle events in Microsoft Access: via {Event Procedure] Event Handlers (i.e., Subs) and Function calls from the Property Sheet.
Subs vs. Functions Event Handlers in Microsoft Access VBA You need event handlers to write event-driven code. This tutorial will help new users get up to speed and may even teach seasoned pros a thing or two.
Subs vs. Functions How to Return Values from a Sub in VBA You can "return" values from a Sub via a parameter passed by reference. What does that look like and when should you use it? Let's explore.
Subs vs. Functions Every Function Has a Return Type Every Function in VBA has a return type even if you don't explicitly define one. In fact, there are *FOUR* different ways to declare function return types.
Subs vs. Functions Why Use Subs at All? Almost every Sub could be a Function...but that doesn't mean it's a good idea.
Subs vs. Functions Subs vs. Functions in VBA What is the difference between a Sub and a Function and why would you use one or the other? I'll give you the short answer...and then we can explore the long answer.