>>I just wanted to make sure it didn't fall into the bit bucket. *s*
>>
>>One thing I had to fight with was making sure that you reset your Document object reference when you ask it to Navigate() because it seems to invalidate the one you had, and you have to wait while both IE is .Busy and wait until the Document.ReadyState = "complete" otherwise the internal collections will give you errors like unknown properties etc.
>
>Actually this is much harder than it sounds <s>... There are several events that you can use but they're not terribly reliable. If you need to navigate to pages and then want to do something for example running a DO WHILE loop to wait for those states has never worked reliably for me even when there's a DoEvents (that one again <bg>).
>
>I have an application that actually renders VFP forms as DHTML and one of the few ActiveX controls other than native controls it supports is the Web Browser control. It worked great except in the procedural enviro0nment the rendering occurs in I couldn't get the timing right to get the thing completely loadded before the rendering started. Very frustrating.
>
>I really wish there was a was to load documents synchronously the way the XMLDOM parser can load docs by waiting for completion.

I have found that waiting for both oIE.ReadyState and then oIE.Document.ReadyState does the trick. Has this failed you?