Hi Dana,

The WebBrowser4 class already has NODEFAULT in the Refresh() event to handle that bug. Placing NODEFAULT in your code overrides class code in that method. If you're not using functionality built into the WebBrowser4 class, you should try to use Web Browser control directly w/o this wrapper class, in which case NODEFAULT in the Refresh(0 will be neccessary.

>
>We have the WebBrowser4 control in use in a form and it works well most of the time, but every now and then someone gets a fatal error when the form is called. It is sporadic. Denis GavriKov pointed out a known bug that is fixed by placing NODEFAULT in the Refresh of the control. That cut down on the errors but has not eliminated them completely. I can't find info on this anywhere.
>
>It happens on different systems, operating systems, etc. If all the users experiencing this error were on Windows XP Pro, for example, at least we'd have a clue, but that is not the case.
>
>If anyone has reliability problems with this control like this and have found a reliable solution please tell me about it. This is driving me nuts, and has caused our data entry users to have to re-enter client information.
>
>If there is no way around this but there is a reliable replacement control I'd like to hear about that as well.
>
>Thanks,
>Dana