>>I'm looking at and trying to understand someone else's code.
>>
>>The situation:
>>
>>- An SCX form based on a form class frmAllBase
>>- On that SCX form there's a Command Button (cmdXLS), based on a hierarchy of command button classes
>>
>>Most of cmdXLS's methods inherit from one of its parent command button classes (as expected). But some of them appear to inherit from frmAllBase (see attached image).
>>
>>frmAllBase is a Form class (with its own inheritance hierarchy) and is no way based on any of cmdXLS's parent command button classes.
>>
>>Can anyone explain what's going on? Is this multiple inheritance of some kind, and if so how was it set up?
>
>There is a class frmAllBase and it has the cmdppzBase on it. So if the dev puts code in the click of the button on the form, you see that, frmallbase, and then on down the button's hierarchy.
>
>Does that sound right?

Yes. As it turns out, when I first looked at frmAllBase I wasn't viewing the whole class. Once I expanded the designer window, yes, it includes a cmdXLS button (based on cmdppzBase). cmdXLS.Click() does indeed contain code.

So, it looks to me like that's the Properties window's way of showing the hierarchy. It makes sense, I suppose, since the class with the parent code is frmBaseAll for those particular methods. In a perfect world it might be nice if the Properties window showed something like [Inherited frmAllBase.cmdXLS ...classlibinfo...]

Thanks for clearing this up, and the VERY specific help :) It sounds like you may have worked on this project in the past?