>I'm not knowledgeable enough to answer that. I believe the number of subclasses is unlimited, but don't quote me. I know that C# supports single class inheritance only - you can specify only one base class to inherit from. However, it does allow multiple interface inheritance. You just can't inherit from multiple base classes (you have to use an interface and dup all base classes). There was a discussion here on the UT about it. The biggest issue was that most see using multiple inheritence as bad design. I think if the business need warrants it, do it. I certainly don't want to open that can of worms again! :o)
Partial classes and extended properties should also be noted. There are a number of ways to do things in .NET that we aren't familiar with in the VFP world. I feel very good with the oop part of fox, but it is interesting to see what else is out there. Since I'm now working with a framework in .net I'm seeing that the idea of subclassing from the base classes and then subclassing from the framework for your own customizations hasn't been lost. It is just done differently - and gets better with each iteration of the .net languages.
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.