>Good object model doesn't make it OOP. Even IE has a good object model, and it still isn't an OOP language. Try to create your own class and subclass it in VB6, without turning it into an ActiveX, and without creating a separate project.
What's the problem with creating multiple classes and subclasses within the same project? You need not to make them as ActiveXs. My coleague that is VB Team leader said that there is no such limitation in VB - to create classes and subclasses in separate projects, and there is no restriction to create subclasses as(from) ActiveX only.
>Of course, neighbor, because it can't be done, but I'm not sad about it. If I had to write an ActiveX, I'd either learn c# or c++, the really OOP languages, rather than take VB. Just a matter of personal preference. Learning to think the OOP way has taken me some time, but once I've done it, I really don't feel like getting back to [pejorative omitted].
C# cannot be used for creating ActiveX - ActiveX is obsolete technology and is not used in CLR and .NET studio. See .NET studio's help for more info. However there are some legacy ActiveX controls available in .NET studio - MaskEdit and MSChart.
