>As for the inheritance issue, it would be great if MS put it in VB, but it is >certainly not the end of the world. People out there aren't dropping VB for >that reason, and why should they? It has some good features to offer. Why >not learn about both products and have the best of both worlds?

The VB folks have a very different view of inheritance than the VFP folks - mostly due to a lack of experience. The way inheritance is *simulated* in VB - makes for a maintenance nightmare. No question that inheritance is often over-used and abused. But nonetheless, it is still valuable and VB would do well to have it. After all, as in VFP, you could simply choose not to use it.


>- Hope I don't get thrown off the Thread for uttering that last statement.....

You will have to take a number behind me... < g >


Thank you for the kind words... :)