Hello Arnon,

My level1 library is _base.vcx the subclassing of VFP subclasses. Level2 is a subclassing of everything in level1 with some added ActiveX controls and composite controls. Level3 is to level2 what level2 is to level1. I though this was a common structure that many used according to devcon seminars. Because the idea is to have each control represented on each level I hate to delete one. If I want a new level3 class that is a subclass of the custom control I could base it on a parent in level3 or level2. I guess it depends whether I want level3's custom control to vary without affecting my new control or not. Do you see my concern about creating a class hierarchy in a way that I won't have to go back and redefine tons of stuff because I did it the wrong way all along?
Thanks for your last response.

>>Thanks for replying. What time is it now in Israel? It is 1am here in Pacific Northwest.
>Here it is now 11:30am
>
>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.
>
>if the classes are identical - i'd suggest you eliminate one of them at this point - unless you know the will differ in the future.
>if they will be different - then you can make your decision based on the future use, otherwise, as I've said delete one of them now - you can always branch the hierarchy at a later time (i.e. add a parent to a class move some of the code to the parent and then create a new subclass with new functionality)
>
>Arnon