Dragan,

You're da man!!! If I knew how to give you the "star" I'd do so:)

>I have read the whole thread. Apart from an extra quotation mark at the end of the offending line (which may have come while you were typing the message, I'll ignore it)

You are correct, I accidentally left in the extra quotation mark and it should be ignored.

>... 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?

>Another thing - unless the layout of your pages prohibits this - is that if you're creating those pages from VFP, so you're in control, why do you have the link to home on the page you show when you're home?

It's a layout thing.

Thanks to everyone (Mark, Gerald) who assisted me with this. Keep up the good work guys.

Mike.