>>>But you cannot add the custom methods (if you need them) to the instance of the default VFP class and can add the custom properties only at runtime with AddProperty method.
>>
>>Ahhh... I got it. So, if I ever need an object that has custom properties or methods I must create a class and an instance. I wonder why? Seems like it would be handy for a couple reasons. First just to have it without the class link if you needed it, and second so the object could be tested fully then saved as a class if it was needed elsewhere. Oh, well... Thanks Nick!
>
>You can do this by designing the object visually in a form and then, when it's working, chose Save As Class. Or have I misunderstood, again?

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. What if I want them, but I don't want the class? 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.