Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP6 security patch via Setup Wizard
Message
General information
Forum:
Visual FoxPro
Category:
Installation, Setup and Configuration
Miscellaneous
Thread ID:
00737599
Message ID:
00737925
Views:
31
Sergey,

I thought the registry.vcx that comes with VFP supports only REG_SZ type values. As to the .REG file approach, this would seem to be OK, except that I would certainly not want to be restricted to Win2K and later. The entry for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\VFPODBC\Q326568 seems superfluous, or do you have some reason to think this is really necessary? Do you suppose that a very simple piece of logic could be constructed to perform this patch with straight API calls and no dependencies on the version of Windows?

I do appreciate your help, and really don't wish to impose on your time. It's hard to believe that no one has already worked this out, and a bit disappointing that MS didn't supply a decent patch in the first place. Surely with their much-vaunted concerns about security, Microsoft could have made it a lot easier for people not to inadvertently propagate this gaping security hole when distributing their own applications.

Mike

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

"Free at last..."
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform