>Very wrong if you ask me that Microsoft allowed (encouraged) developers with VFP 6.0 to develop applications using the Web Control and now after many hours of development time invested to integrate the control into an application Microsoft now says I MUST install Internet Explorer to use that control. I would have NEVER used the control if this were the policy when I started developing this application. Many of my users are using Netscape as a browser and do not want to install TWO applications in order to use ONE application. The attraction for me to use the Web Control in the first place was it allowed me to generate DHTML output that worked in IE’s DOM regardless what browser was or wasn’t installed on the computer. Talk about classic bait and switch! Does anyone else find this WRONG?

The webbrowser control is basically IE. Both IE and your app use the same exact DLL's, so you can't install one without getting the other. Your users don't need to use IE (even though your app requires it) for their normal browsing. I guess you could remove the shortcut to IE from the desktop if you want.

I can't say the licensing bothers me too much. I basically get to use a very powerful COM component and include it in my applications for free. IE is already included with the operating system, I just distribute the latest version of it. The users don't have to use it directly if they don't want to.