I just tested what you are saying, and you are absolutly right.

In 6.0 I execute from the command window:

oX = createobj('word.application')

and, in the debugger local screen, I see the variable with a description of object, but I can't drill into it.

In 7.0 if I do the same steps, in the debugger I can drill into the object reference and see the properties and values. (You learn something new every day.)

Also, as someone was saying, 7.0 adds the Object Browser so you can look at the properties, methods, enums, types of properties and parameters, etc. This makes working with third party COM/ActiveX classes much easier. Tamar added that since VFP now can get this info, it is also used by intellesense when you are coding to give you on the fly info of a COM objects members.

I really think you will like 7.0!

BOb

PS: As someone said, in the early Visual Studio 7.0 betas you would be able to step into a VFP COM object as it was executing. It allowed you to say start debugging in an ASP page, and if the ASP page used a VFP com object, the debugger would jump into the COM object and trace that also.

>Hmmm... Now you've got me worried. I don't mean "step into" in the sense of being able to follow the internal execution of an external COM object, I just mean, for example, being able to expand the object structure under an oWebBrowser.Document object. Are you saying that the VFP 7 debugger is just as lame as the VFP 6 debugger in this respect? That would be a major bummer. I guess I'll have to go back to being the blind man in the forest, if that's the case. Do you ever get the sense that someone is trying to make life difficult for VFP developers? We'll just have to be like the blind swordsmen in all those samurai movies.
>
>Mike