Don't forget, when you copy and paste the control, the event procedures do not come along for the ride. You have to copy them separately and then to make sure they connect to the new form controls, open each event procedure.
Yes, I was just coming to that. The funny thing, though, is that sometimes just copying code over from template to new form doesn't automatically register the event, and the code won't be invoked at all. For example, if you copy the code from the line
Private Sub btn_Click() all the way to
End Sub and paste it over, sometimes the code in there will be ignored and nothing will happen when
btn is clicked. The proper way would be to go to the [Events] page in the control properties, find the [On Click] even, click the [...], and paste just the inner code when the code editor opens and generates the procedure for you. Really took me a lot of time to figure out why the code wouldn't run. I don't know if this is a bug or what, but it's kind of annoying.
I read somewhere that if you use macros instead of VBA, then they will always be attached to the controls wherever you copy. But I'm really clumsy when it comes to macros. They're just confusing.
Other than that, things look pretty good for now, and I'm still working on it in my Access time.
In the meantime, I also find MajP's FAYT quite interesting. In my project I have a lot of those FAYT combo boxes and textboxes myself, not created in the most efficient ways of course, and certainly not instantiated out of class modules. This will be great learning material for me. Some of those other implementations from the above links are beyond my level at this point, so I'll start with this one first to learn about class modules. Thanks MajP.