What I was trying to clarify is if the button is an HTML [web page] button or a VFP command button class. If it is an HTML button, then I do not see how this is an object that can be manipulated by VFP. I think I understand your problem. I think you can not reference the document objects until the document completely loads. I would think putting that code in the DocumentComplete event would work.

>In case you haven't figured it, I'm a rookie "web developer" too.
>
>I don't know if I understand you when you said that you cannot reference any "object" on the page after it is returned to the browser. I've been able to manipulate "objects" in the browser control as follows:
>
>I put a VFP command button on the same form that also contains the browser control on it. The browser control is displaying the page that contains my Home button. If, in the click event of the VFP command button, I place "thisform.obrowser.document.frames(0).home.disabled = !thisform.obrowser.document.frames(0).home.disabled" I can see the Home button become enabled/disabled as expected! This works great.
>
>My problem is that I have to make VFP issue the command to do the enabling/disabling of the Home button via the VFP command button. I can't find a way to automatically have the Home button enabled/disabled after navigating to the Home page. It wouldn't make sense for the end user to have to click a VFP form button to then refresh objects on the browser control's document.
>
>I hope that some of this makes sense. And thanks again for your assistance with this problem.