Hi Jim,

>Doesn't your test reveal that VFP 6 does, indeed, "register" with IE (but that it does not do it "properly")?

Registering with IE simply means to have information in the registry that tells IE, whether it should ask the user before opening a file after download. Think of Word or Excel files: they're opened immediately when you click on a link that points to a doc or xls file. If you click on a link to an EXE or ZIP file, you're asked, whether you want to open or save the file. VFP6 regiters app files the first way, VFP7 the latter way.

>I ask because the "Microsoft Security Bulletin MS02-49" says "Visual FoxPro 6.0 does not perform this registration....
>It seems legitimate to assume that if it did not perform the necessary registration, then your VFP7-performed registration should have remained and thus protected you.

If you're installing VFP6 after VFP7, VFP6 overwrites the registry information for app files, VFP7 has supplied.

But this is even worse with MS Office products (or at least it was, I don't know if this has changed nowadays). If you were running Excel 5 and 6 on the same machine they always registered themselves on startup for the Excel file extensions. So it always depended on the version you had started the last time, launching the exe file, which version was started the next time you opened an XLS file in Explorer.

Armin