>>lncomplete=4
>>do while readystate<>lncomplete
>>enddo
>
>Well, it was even easier than that but you gave me the clue to the solution. I had a form Refresh() call right after the Navigate2 and this seemed to be causing the problem. I still don't know why it worked on one machine and not the other, but moving the Refresh() to the browser DocumentComplete event made the problem go away.

Yeah I've written a few small apps that use the wbcontrol and the documentcomplete property USUALLY works for what I need. Sometimes you have to do a loop to check for the existence of the object that documentcomplete occurs in though otherwise, it will bomb from time-to-time.