Jim,

>So the wording is misleading in the bulletin!
>The full statement in the "Technical Details" of the bulletin is: "In general, when an product installs, it should register itself with Internet Explorer. This allows the product to specify how Internet Explorer should handle files associated with it when referenced from a web page – for instance, it allows the product to specify whether the user should be presented with a warning dialogue before such a file is opened.
>
>Visual FoxPro 6.0 does not perform this registration . . .".

>Any reader would be correct in assuming that VFP6's install does NOT tamper with registration at all, but in fact it does! What it does not do, but is not clearly stated, is "register" the extensions properly! There is a big difference. Sure, "informed" readers might be able to infer the subtle meaning, but I don't think that is acceptable to risk.

Well, VFP registers the app extension regarding what exe should be launched and how the exe is called when an app file is being executed.

Whether we should see the option "ask before opening this file after download" as part of Windows or IE ... I don't know. The option is being displayed in a dialog of the Windows OS, but it seems to be used by IE only (AFAIK - pls. see my latest message to Dragan).

If we see the option as part of Windows, "doesn't register the file extension 'app' properly" would probably be a better phrase. If we see the option as an IE setting (that just happens to appear in a Windows dialog), the phrase supplied is ok. I think this is more a 'political' issue ... integration of Browser with OS ...

IMO the only thing that is really missing is the fact, that the installation order (VFP6 and 7) is important in regard, whether you need to apply the patch, or not.

Regards,
Armin