>>One thing I noticed when handling oExcel is that the interface to it (and to browser object as well, not necessarily related to this) is quirky, at least. One thing that it doesn't like is going too deep in a hierarchy of reference. Some things like
>
>That has been my experience as well. And it seems to be that case for most automation (ie. Outlook, internet explorer, Word, Excel). Everytime you change level in the hierarchy make a reference to it. Here is perfect example, the internet explorer document property.
>

o = CREATEOBJECT('internetexplorer.application')
>o.Navigate2("www.microsoft.com")
>o.Document. && Nothing show up here

>
>And yet if you do this
>
>

o = CREATEOBJECT('internetexplorer.application')
>o.Navigate2("www.microsoft.com")
>oDoc=o.Document
>oDoc. && Now the properties show up

Exactly the same as I see it when I try it. Though, I never use that particular url :).