No it does not.

1. The Class Browser is a fine tool, but somewhat buggy. It constantly causes VFP to crash when traversing the class ancestory.

2. There is no way to produce a code output that has all of the ancestory code in one file. You can only view the class code for one class/class library at a time.

3. There is no way to see subclassed children. If you do not know what the children are already, there is no facility for tracing them other than searching through the entire class libary file folders.

In other words, the VFP class facilities are limited and kind of klunky. This is being amplified in my world as I am learning a new language called Eiffel, where even the programming environment (EiffelBench) is object oriented. Anyway, the reasons noted above are why I am looking for something far more comprehensive.

Regards,

Larry