>Thanks for your responses; I was beginning to wonder if anyone thought this was worth replying to... I guess using my example through everyone off a bit. I was interested primarily in knowing whether the logical relationship between the class and the instances was such that the class should contain behaviour/code that was shared and the instances only what was relevant to it's particular environment. I was really trying to draw a line in the sand regarding what to code in an instance as opposed to in the class. Dan mentioned that I should put the AddProc in both buttons as this was only relative to the form. I think I agree, but where is the line drawn? Does that mean that it would be ok to put it in the class if my classed forms always contained that proc? Or would it never be ok? Again, that's just an example; looking for concepts really. I'm trying to develop apps with the mindset of relatively easy mainenance as well as solid functionality. It gets a bit fuzzy in reality as to
>where to put what sometimes...
>
>Renoir

I think that maybe a book would do better than I would talking about general principals and why things should be coded in an instance as opposed to a class. It seems to me That Jim Booth has some good white papers on his website about this subject.

As a general rule the more a class can be like a black box, only really knowing about itself, such as a button class, the easier it is to use and re-use that button.