John,

Please bear with me. I've been doing my own testing, which indicates that the HKEY_CLASSES_ROOT\Visual.FoxPro.Application.6\EditFlags registry setting does not affect IE's willingness to launch an Active Document without prompting. Isn't that the point of the patch? Are you sure there isn't some other required registry setting? I just want to distribute a VFP6-based setup program that does this correctly and unobtrusively.

Update (1/19/03):

OK, I see the cause of my confusion: I was doing preliminary testing of my new VFP6 security patch logic on a machine with VFP7, on which I have not run my VFP6 Setup Wizard-generated runtime setup.exe. Consequently, the .APP extension on this machine is associated with Visual.FoxPro.Application.7, so changes to Visual.FoxPro.Application.6 have no effect on IE's behavior toward .APPs. If I were to run my VFP6 runtime setup on this machine, and if it reverts the association of .APPs to Visual.FoxPro.Application.6, the registry edit you suggested would properly force the prompt to "Confirm open after download". On the other hand, if running a VFP6 runtime setup on a VFP7 machine leaves .APPs associated with Visual.FoxPro.Application.7, then it would have no effect on IE's prompting for .APPs, so the VFP6 setup would not introduce any security problem. In either case, clearing HKEY_CLASSES_ROOT\Visual.FoxPro.Application.6\EditFlags should either fix the problem, or be irrelevant.

Mike

>Ummm...different relationship between the hives, GT. Changing the reg entry in CLASSES_ROOT solves the problem for the other hive. Trust me - I tested the crap out of this ;-)
>
>
>>>Nope......CLASSES_ROOT replicates down to the LOCAL_MACHINE hive automatically.
>>
>>Gonzo,
>>
>>I believe that HKEY_CLASSES_ROOT is actually a sub-hive of HKEY_LOCAL_MACHINE in the same manner that HKEY_CURRENT_USER is a part of HKEY_USERS.