>So, I made another method with my conversion function...but then I also found that I have a leapyear function within the conversion function....and before adding another method to the form, I began thinking, maybe this isn't a "best practice".

What you could do is create a new class based on a Custom Object, that just has the properties and methods you need. This could have ALL your generic routines, or maybe this one will just have your date routines, whatever you choose. But once you have that object, you can drop it on the form or create it in code and thats typically how I do those things.

PRGs still have their place in our development, but when it turns out you can logically class variables and procedures togather, a class might be the best way to go.