Hi Hugh,

I solved the problem by placing a DOEVENTS in the DocumentComplete event where the troublesome line of code now resides. It appeared to be a "timing problem" that DOEVENTS somehow resolves.

I don't know if you've followed the complete thread, but, as I'd explained before, VFP had no problem referring to the Home object and seeing its disabled property in the debugger's watch window!!! The problem only appeared when it tried to execute the line of code. Once I suspended the code (after the error occurred) and went to the watch window, VFP could see the object no problem.

I appreciate you help and thank you for trying to assist me with it. Hopefully, I've shed some light on this issue for anyone else experiencing the same problems.

Mike.

>Hi Mike,
>
>Damn! I knew this one would get under my skin!!!
>
>OK, try this:
>
>OXX.IEBROWSER.DOCUMENT.FRAMES(0).DOCUMENT.BODY.ALL.ITEM("HOME").DISABLED=.T.
>
>Where OXX is the object handle to the form
> IEBROWSER is the browser control's name
> HOME is the button's NAME or ID
>
>Good luck!!!
>
>Hugh