>>All VFP classes must eventually be based on the native VFP classes.
So, yes they are. <<

Well, I sure always thought they were - guess I was just looking to hard.

>>(eg. subclasses of other MM classes, which may be subclassed from other MM classes, which eventually leads down to the native VFP controls). <<

And this was what was probably confusing me (among other things <g>). Lots of subclassing going on, but the more I read and work with MM, better I see what is going on here.

>>Hope that helps (and my explanation doesn't confuse you) ;-)<<

Paul, it sure did. Thanks a million.

Mel Cummings