If there are more than 3 controls I'd probably use the tag approach mentioned in post 2 rather than have a sub for every one of them since the number of controls needing this sometimes grows as things change. The worst part of the multi sub approach is that one usually codes to exit if a required field has no value. User fixes that and tries to save again only to encounter another annoying prompt. I avoid that by listing all of them at once in one message box. I also like to ensure that the labels for these controls are attached. That way, I can get the descriptive text for the field (e.g. First Name) from the label rather than the name of the control (e.g. txtFName). However, I would have that situation because I never allow a field and control to have the same name, and the field names are often shortened since they only need to make sense to me.
@a.phoenix, if you want some code that handles all this, I should be able to find it in my archives. You would need to add a tag - e.g. Reqd (no quotes) to the tag property for those controls that require this validation. Also best to limit the search in the code to only the type(s) of controls you've done this for so you'd need to define that in a post.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.