>>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.
>
>VFP6 debugger knew those properties of a COM objects which were specifically mentioned in code (or in command window). VFP7 knows all the properties in advance by reading the typelib of the COM object, so they are available to both the debugger and intellisense (you can pull up the command window while debugging, type oWord. and all of its PEMs just drop down for you to choose from).

Magnifique!