>But wouldn't it have a window? I didn't see anything whose class name resembled ListImage or ImageList.

Not necessarily. An image (icon, bitmap, etc) doesn't have a window/hwnd, but a handle (HICON for icons). As I said, I never worked with these controls, but, as far as I understand, the ListView control keeps a list of imgages in a ListImage control. It probably uses these images to draw them on its own client area, so there's no need for a hwnd for each image.

>The MFC ActiveX control wizard lists both the SysListView32 and SysTreeView32 among the windows that can be sub-classed. Since more common objects like command buttons, etc are included in the list, I would assume that it does use MFC. However, like you, I'm just guessing.

Nope, it's the other way around. MFC supports ActiveX/COM controls/components. Basically, you can add any COM to the list of components used by the MFC's wizard(s). So, these controls can be used from VC++ programs built on MFC, but these controls do not (necessarily) use MFC.

As I said, MFC is just a collection of C++ classes and wizards. It's like a third-party framework in VFP.

Vlad