>I too have always found it odd that Intellisense would pick up a list of properties but the debugger wouldnt.
>If there is something to make it, then I personally dont know it, but would love to :)
>
>Ken and Dragen's messages both seem to say that it can. Which would lead me to believe that they are either mistaken in their beliefs, or there is something you have to do to make it read them. I go for the later of thoes two.

This is absolutely incredible - I was trying to do the exactly same thing that Mike is doing (OK, I confess, I'm learning JavaScript :), and I just take a peek at UT and here it is. A thread about the thing I'm banging my head on.

It seems to be pretty much what Tamar says - depends on the server. I've written that the debugger gets to read the type library and that's how it gets to be so smart, but it seems it can't be much smarter than what it can't read.

I've seen even weirder stuff within the last two hours. Try this:

goWeb = CREATEOBJECT("internetexplorer.application")
goweb.Navigate("{here goes an URL with a form on it}")
ofr=goweb.Application.Document.forms[0]

Now fire up the debugger. If ofr doesn't have any properties, try ?ofr.elements[0].value from the command window, and then look at ofr in the locals window again. It has an elements property now, with a + to it.

do while .t.

Now try to click that plus... what you get is that the elements property has an elements property which has a + to it.

enddo