>>>>
>>>>I did download and create a installation package using the wizard. Yes, it is easy to use and is nice if you want to create a "standalone Explorer" application. All I need is the latest web control. My frameworks hosts the control as one of the interfaces it provides. All navigation is provided by the framework's Outlook bar and Treeview control.
>>>>
>>>>The thing with VFP 6.0's "Microsoft Web Browser" control is it gave me just the control itself. Plus it gave me whichever version of Internet Explorer I had installed on the computer creating the setup application. This is all I want. There must be an easy way to do this?
>>>>
>>>>I am going to try to use InstallShield's Dynamic Scanning Wizard to detect just the DLLs I need.
>>>>
>>>>Anyone know what the WebClassRuntime merge module is?
>>>
>>> The problem is that the Microsoft license doesn't allow you to do this anymore. You have to the IEAK if you want to distribute the control. While there is no technical reason why you can't just distribute the required DLL's, there are legal reasons why you can't.
>>
>>Paul,
>>
>>Does your reading of the Microsoft licensing restrictions carry retroactively to people who distribute applications built with VFP 6.0?
>>
>>Mike
>
>I guess that depends on the license as of that time. This is the first app. I've done where I needed to include the control, so I haven't looked at the licensing until recently. The current agreement basically says you're bound to the terms of the agreement for one year and will automatically be renewed unless either party wants to make changes to it.

Hmmm... Thank, Paul. I guess it would be helpful to get some clarification straight from the horse's mouth about this.

Mike