>>... sounds like a timing issue. How about issuing a dodefault(), and maybe a doevents() before setting this .disabled property? I don't really know when does navigatecomplete2 fire, exacrly after the page has finished loading, or is there some slight delay.
>
>You were again correct. I put a DODEFAULT() AND DOEVENTS() prior to setting the property and this WORKS!. I no longer get the error. It is definitely a timing issue since now that it works I notice that my Home button does become disabled, but, it does so after about a second or two. Perhaps the page is still loading even though I can see (some of) it and it only appears to be completely loaded. If this is the case, then why does the NavigateComplete2 event get fired?

Maybe the rest of the load happens in a different thread, and the navigateComplete2 receives a message from that thread before it actually finishes. Happens a bit asynchronously, it seems.