Thanks, Sergey. That certainly is a relevant reference, but I guess the original question never got resolved. My preference would be to avoid any WSH dependence by using some simple API calls. I assume the essential logic boils down to making a substitution for these 2 lines:

=oshell.RegWrite("HKEY_CLASSES_ROOT\Visual.FoxPro.Application.6\EditFlags",0,"REG_DWORD")
=oshell.RegWrite("HKEY_LOCAL_MACHINE\Software\Classes\Visual.FoxPro.Application.6\EditFlags",0,"REG_DWORD")

With my very limited experience in registry manipulation, this seemingly trivial task is enough of an obstacle that I'm still inclined to punt with the imperfect solution of simply invoking vfp_q326568_en.exe for now. Optimization of this step will go into my very large list of further enhancements to be dealt with later, unless someone happens to hand me the solution on a silver platter ;-) If I work it out myself, I'll post the code.

Mike

>You may want take a look at Writing to the registry during setup - vfp6 Thread #729505.
>
>< snip >
>>
>>Whether option A. is permissible depends on Microsoft's position as to the inclusion of this file in a distribution. I imagine that I could figure out how to implement option B, but it would be nice if anyone has already worked this out and would be so kind as to post the exact code. This is, after all, a totally generic issue that applies to any VFP6 Wizard-generated setup. It would be great if someone at MS could jump in and provide a little assistance (hint).
>>
>>Mike