>:
>: >I've been using MS Webbrowser control in OLE automation for several
>: different projects now (HTML help and Internet linking of apps). Now I'm
>
>: distributing my app and I tried to go looking for the simple OCX file I
>: thought was the Webbrowser control.
>: >
>: >WRONG
>: >
>: >Turns out Webbrowser is built into MS Internet Explorer. You can't
>: separate it out and thus if you use MS Webbrowser, all client
>workstations
>: must have the full MS IE 3.0 or later installed.
>: >
>: >Netscape, are you taking notes on how to do buisness?
>:
>: I guess that's why we are better when using the HTML OCX instead. :)
>
>not really , considering that MSIE is free..
>
>Arnon

I'm not complaining about the price. Free is great. It just strikes me as an interesting business decision not to make a separate webbrowser.ocx file and forcing one to use the full MSIE install.

Michael, does html.ocx support ole automation?