>Although multiple inheritance would be great, I'm not sure Microsoft knows how >to use it (contrast MFC with OWL.) I would settle for Java style Interfaces.
>Multiple constructors (or Init() methods) with typed parameter declarations >would be nice. I hate having to check for the existence and types of >parameters.

I totally disagree here.. Saddling VFP with multiple-inheritance would utlimately cause more harm than good. On the other hand, having 1 root abstract class that could be used would make it easier to define common attributes and behaviors. Of course, with VFP's superior containership model - aggregation gets us around the problem quite nicely.

If you want/need multiple inheritance - there are other tools that do support that.