Hi Michel,

You can use registry.vcx that comes with VFP. Or you can export registry entries into file with .REG extension and run it on destination computer using SHELLEXECUTE(). Hre's the file for WIn2k and later

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Visual.FoxPro.Application.6]
@="Microsoft Visual FoxPro Application"
"EditFlags"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Visual.FoxPro.Application.6]
@="Microsoft Visual FoxPro Application"
"EditFlags"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\VFPODBC\Q326568]
"Description"="Microsoft ODBC Driver QFE Q326568"
"Type"="Update"
"Installed"=dword:00000001

>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
>