Fornatian
Dim Person
- Local time
- Today, 14:25
- Joined
- Sep 1, 2000
- Messages
- 1,396
EXACTLY.
You never have to type anything twice which is commonly used. They are not the panacea though, you have consider whether there is any real advantage in building a public sub or function. This is generally determined by the number of times it is called and how standard the actual tasks are.
PS. The PrintOrPreview procedure could actually have been a sub (because it doesn't return a value but I converted it to a function so that I could call it from the event procedure tab. Instead of building a VBA click event you type:
=PrintOrPreview("YourReport")
in the space for the click event which normally reads [Event Procedure] when there is an associated event. see attached gif
You never have to type anything twice which is commonly used. They are not the panacea though, you have consider whether there is any real advantage in building a public sub or function. This is generally determined by the number of times it is called and how standard the actual tasks are.
PS. The PrintOrPreview procedure could actually have been a sub (because it doesn't return a value but I converted it to a function so that I could call it from the event procedure tab. Instead of building a VBA click event you type:
=PrintOrPreview("YourReport")
in the space for the click event which normally reads [Event Procedure] when there is an associated event. see attached gif
