Renoir-

>I think so, but it might be me. :) If I can't visually add custom methods or properties to an object on a form, and I need them, I must create a class.

Ah. I see. Yes, by all means make a class with empty methods and properties. Or just comment out all your custom code in your class you have and try re-adding it bit by bit, testing along the way.

> What if I want them, but I don't want the class?

This I don'tunderstand. Every combo you drop on in a container is an object. It's an instantiation of a class. Even if you use the basic one. It's an instantiation of the baseclass combo. Once an object exits, it's pretty much fixed. It's even questionable, tho' useful, OOP practice to even add properties to an object.

> After what I've gone throught the past few days with my combobox/focus issue (now referred to as Combo666) I was hoping I could just have an object with all the funtionality of the original class in order to just try and get it to work.

Er, well, you don't really want _all_ the functionality, right? The bad bits.