Hi Rick,

Thank you very much!

>Hi Dmitry,
>
>It used to be standard practice to install the VFP runtime files in {cf}\Microsoft Shared\VFP, mostly because that's how the VFP runtime merge modules from Microsoft were configured. Since quite a while ago, the conventional wisdom is now to install the runtime files in the {app} folder. This avoids conflicts with other versions of VFP runtimes on the same machine, as for example the VFP9 SP1 and VFP9 SP2 runtimes share the same file names and therefore cannot co-exist in {cf}\Microsoft Shared\VFP.
>
>Below is the Inno Setup script I currently use for VFP9 SP2 runtime and related files (the source folders will be different on your machine). You can copy it inline into the [Files] section of your installer setup script, or (what I do) save it as a .txt or a .iss file and simply #include it. Of course, you may need to add or modify as required for your app.
>
>;**********************************************************************
>;
>; VFP9 SP2 runtime support libraries and related files
>;
>; NOTE - This version installs the VFP runtime files to the
>; application directory, not to the Common Files directory.
>;
>;**********************************************************************
>; Microsoft Graphics Device Interface Plus (GDI+) DLL
>Source: C:\VFP9Distrib\VFP9SP2_RuntimeFiles\gdiplus.dll; DestDir: {app}; Flags: restartreplace
>
>; Microsoft Visual C++ 7.1 Runtime DLL
>Source: C:\VFP9Distrib\System32\msvcr71.dll; DestDir: {app}; Flags: restartreplace
>
>; Microsoft Visual FoxPro 9.0 Runtime Support Libraries
>Source: C:\VFP9Distrib\VFP9SP2_RuntimeFiles\vfp9r.dll; DestDir: {app}; Flags: restartreplace
>Source: C:\VFP9Distrib\VFP9SP2_RuntimeFiles\vfp9t.dll; DestDir: {app}; Flags: restartreplace
>Source: C:\VFP9Distrib\VFP9SP2_RuntimeFiles\vfp9renu.dll; DestDir: {app}; Flags: restartreplace
>
>; Microsoft HTML Help Runtime Files for Visual FoxPro 9.0
>Source: C:\VFP9Distrib\VFP9SP2_RuntimeFiles\foxhhelp9.exe; DestDir: {app}; Flags: restartreplace
>Source: C:\VFP9Distrib\VFP9SP2_RuntimeFiles\foxhhelpps9.dll; DestDir: {app}; Flags: restartreplace
>
>; Microsoft Visual FoxPro 9.0 Object-assisted Reports
>Source: C:\VFP9Distrib\VFP9SP2_Reports\ReportBuilder.app; DestDir: {app}; Flags: restartreplace
>Source: C:\VFP9Distrib\VFP9SP2_Reports\ReportPreview.app; DestDir: {app}; Flags: restartreplace
>Source: C:\VFP9Distrib\VFP9SP2_Reports\ReportOutput.app; DestDir: {app}; Flags: restartreplace
>
>; Microsoft MSXML 3.0 required for XMLTOCURSOR()
>Source: C:\VFP9Distrib\MSXML3\msxml3.dll; DestDir: {sys}; Flags: onlyifdoesntexist regserver sharedfile restartreplace uninsneveruninstall
>Source: C:\VFP9Distrib\MSXML3\msxml3a.dll; DestDir: {sys}; Flags: onlyifdoesntexist sharedfile restartreplace uninsneveruninstall
>Source: C:\VFP9Distrib\MSXML3\msxml3r.dll; DestDir: {sys}; Flags: onlyifdoesntexist sharedfile restartreplace uninsneveruninstall
>
>; Microsoft MSXML 4.0 required for XMLAdapter Class and HTML/XML Report Output
>Source: C:\VFP9Distrib\MSXML4\msxml4.dll; DestDir: {sys}; Flags: onlyifdoesntexist regserver sharedfile restartreplace uninsneveruninstall
>Source: C:\VFP9Distrib\MSXML4\msxml4r.dll; DestDir: {sys}; Flags: onlyifdoesntexist sharedfile restartreplace uninsneveruninstall
>
>HTH,
>
>-Rick
>
>
>>A few more questions, please:
>>
>>1. I looked at my InstallShield old setup and I see that during the installation on a client PC the files would be copied to folder:
>> \CommonFilesFolder\VFP
>>
>> The sample Inno script created by Rick Borup stores the files in the folder {cf}\Microsoft Shared\VFP.
>>
>> How significant that is to have "Miscrsoft Shared" folder between {cf} and VFP? At run-time, does client PC include ALL folders under the {cf} in its PATH?
>>
>>2. My setup needs to include 2 .ocx files (ActiveX). In the InstallShield they would go to the {cf}\VFP folder, which is the same I want to do in Inno. But these .ocs files have to be registered. How do you specify in Inno that these files have to be registered and not simply copied?
>>
>>3. If I change the folder name {cf}\VFP to {cf}\MyAppName would the Setup still work? (this kind of coming back to the question 1, if all folders under {cf} are in the PATH.
>>
>>TIA