Directly from the ActiveX control.

>Just wondering . . . is this the web browser found in the FFC or did you subclass it directly from the ActiveX control?
>
>>Bo,
>>
>>Adding a _VFP.AutoYield = .T. before DOEVENTS seems to help, so perhaps in some cases it was going off? How would that occur?
>>
>>Thanks,
>>
>>Alex
>>
>>
>>>Hi Alex,
>>>
>>>>The navigator is timing out, even when I increase time to 8 seconds, but only sometimes (often).
>>>>
>>>>What could be causing the problem? Maybe some properties are set wrong? I created the class some time ago and haven;t used it much.
>>>
>>>I have had bad luck with this type of loop waiting for the WebBrowser control:
>>>
>>>

>>>>>>	DO WHILE toBrowser.ReadyState # lnReadyState AND lnX < lnMilliSeconds
>>>>>>		DOEVENTS
>>>>>>		lnX = lnX + 1
>>>>>>		Sleep(1)
>>>>>>	ENDDO
>>>

>>>
>>>Even the DOEVENTS / Sleep combination do not seem to be enough to allow the control to do it's job. But stepping through the code does. That's what makes this fustrating to debug.
>>>
>>>I would try one of these 3 things:
>>>
>>>1) Change your DOEVENTS to DOVENTS FORCE
>>>2) Make sure _VFP.AutoYield is set to .T.
>>>3) Don't use a loop to wait for the browser to finish, instead hook into the NavigateComplete2 event. This is similar to a CallBack and is the preffered methodology for dealing with Asynchronous processes.
>>>
>>>I hope this helps,