Larry-

>It is very difficult to analyze and debug code in situations where you have a form that has multiple classes embedded within it. It would be of immense help to all VFP developer if we could have a window at both design time and in debug mode where we could see the following...
>
>1) The different class layers for a selected object.

If you select an object on a form and then select classbrowser from the menu, you get the class library open. Frankly, I don't want to see this normally, only by exception. I try very hard to not be debugging multilple inheritence levels at a time. The catalog manager is probably also a good tool. Am trying to learn how to use that better.

>2) The hierarchy (i.e. order) in which an object's code would go normally go through.

I don't see how #1 and #2 are different, so probably I'm missing something.

>3) Be able to see the bypassed/overridden code, so we can see if we have overridden any needed code by mistake.

VFP 7.0 does show you this in design time. Which class you inherit from. That's very nice and helpful, IMO.

>At design time, for example, if we could right click on an object and select a "Code Hierarchy" option, and have a "Code hierarchy window" (similar to the current code window) where we could choose a method and then have the system show us (read-only) the code in order of execution.

See my point above about the Class Browser. I realize it's not really what you're looking for.

I suggest that you post each wish seperately to foxwish@microsoft.com (I think that's the correct email.)