>Thanks for the quick replies! I can fully understand creating a class for something if I were planning to use it in other apps, but for me (the company "QA-manager-turned-programmer-cuz-it-needed-to-be-done") there is only one app on the horizon :)
>
>And fear not....I'll be needing lots of good help. I'm off to investigate the premier membership now!

Actually, another reason for creating a class, even when you don't think you need to, is that you usually end up needing too ;-) Honesty, I can't tell you how many times I've written something, not thinking I'd need it anywhere else, then suddenly I needed it somewhere else.

Classes are pretty easy to create, only require a little more work, and have a lot to offer. Just ask yourself the question, "how can I make this reusable and generic" while writing the class. For instance, instead of hardcoding something like a window title, create a property for it instead. Now it's a little more generic and can be overridden later if you decide to subclass it (or use it in another app).