Hi ken,

I don't know if you've been following this thread, but, I reported "solving" the problem by placing a DOEVENTS just prior to the code where I want to disable a HTML button in the NavigateComplete2 event. While this worked ok under VFP6.0, it failed on a second computer running VFP7SP1.

Now I've placed the exact same code in the DocumentComplete event and this works under VFP7SP1! I don't know how this will impact the code running under VFP6 but I think that I tried it previously and it caused the error. I will have to wait until Monday to test it out.

Have you ever heard of anything related to the versions of VFP and their compatibility with the web browser control?

TIA

Mike.

>There is a ReadyState property, but sometimes you need a DOEVENTS in a loop to keep firing if you are waiting for it in a loop. I have used the DocumentComplete event to know when it is done loading the document.