>Well, I've read some articles that doing so by MS is totally re-writing the whole architecture of the product. With that said, backward compatibility with the current systems done in VB is a big issue. Take a look what happened with VFP, version 3.0 has a lot of headaches and it only started to stabilize with the release of version 5.0 but the damage has been done. Only now it begins to recover slowly because VFP is well architectured and is capable to play with Windows DNA and COM world. You know what, inheritance is really an important feature when it comes to UI design and implementation.

Sorry but I will believe when I will see. Imagine all the VBA in all these applications. If they want to do good job, they have to implement it in VBA too. And what about VBScript???

There were rumours at sometime (a little before VB5) that the inheritance feature was ready but due to the large number of people who aren't programmer and they use VB (or VBA or VBScript), MS didn't want to let them play with it.

They must have done much like Borland: Build a new environment/compiler (called Delphi) based on an already existing product (Turbo Pascal) but not saying that projects are fully upgradable from the latest to the newest. Saying that, they don't have this damn backward compatibilty that steals a lot of nice features.

I want to say that it is my opinion!