for inadequate documentation. This was never something I could get too excited about.
>
>On the other hand, it sounds like the improvements in VFP 7's debugger will make a huge difference in my ability to probe the complex world of ActiveX controls and OLE Automation. Where VFP 6's debugger just displays a single impenetrable (object), VFP 7 actually reveals the hairy underlying structure! Gadzooks, man, how could Microsoft fail to mention this? I feel like a blind man who has been trying to map out a forest by poking around with his cane.
>
>I hope this information will be helpful to your research on the reasons for people's delay in upgrading to VFP7. I would also hope that somehow you will find a way of adding this point conspicuously into some of the appropriate places that summarize what's new in VFP7. Intellisense may have a nice ring to it, but it's hard for me to see how any serious developer would fail to be vastly more interested in the improvements to VFP7's debugger. That's my 2 cents worth.
>
>Mike

PMFJI - but, that's exactly what Intellisense lets you do (along with the Object Browser which works like the object browser in VB). It automatically pulls this info out of the components type libraries for you. It also lets you do this on against a web service running on a remote system. Very cool. You don't need to do this via the debugger, you can do it right from your code, or the command window. With the object browser addition you can do things like drag and drop an objects event list into a code window and VFP with automatically create the interface code for you (for binding COM events to VFP code). That's in addition to being able to browse objects in a treeview structure with all the comments for methods.