Thanks for replying. What time is it now in Israel? It is 1am here in Pacific Northwest. The two potential parents in this case are exactly identical at this time. That is why there is a question. Whenever there is a choice, and I can find no obvious reason to go one direction, I wonder if there is a standard or reason I don't see. Both parent potentials are the custom class on different class hierarchy levels. The reason these identities exist is for future potential for specialization at the level that it is needed. TIA.

>>I am starting to construct more abstract classes and wonder how people are deciding to choose the source of parent for their new classes. If I use a subclass of custom in a 3 tier class hierarchy I would have two choices. If I create the new class in the third app tier, I could subclass either the custom class in the third tier or I could subclass the parent of the custom class in the third tier. I realize there is not much difference here, but since this activity seems that it could become addictive it would be nice to have a consistent method that had some reason to it. Subclassing the third tier custom class actually gives one level more of specialization potential. Is that why it is the best?
>
>Deciding which class should be parent of your new class depends on the functionality of the new class and the relation if bears to its potential parent classes - how much of the parent class functionality does it extend/supercede how much of the parent class functionality is needed etc.
>
>Arnon