It is far better than the installer (nameless) that comes with VFP

>Thanks Neil, nice to know that INNO SETUP can handle this. I really like the power and flexibility of this free utility.
>
>>Check out the files section and the regserver flag. I have have given an example of registering vfp9r.dll below:-
>>

>>Source: .\Distrib\vfp9r.dll; DestDir: {cf}\Microsoft Shared\VFP; Flags: regserver sharedfile uninsneveruninstall restartreplace
>>

>>
>>>Nice, so this is going to be a distribution SETUP.EXE for end users. What steps need to be taken for them to do the registration of the DLL or can this be automated for them in some fashion?
>>>
>>>>Tom,
>>>>
>>>>You don't have to bother with .MSM or .MSI. All you have to do is distribute VFPOLEDB.DLL and register it on the destination PC.
>>>>
>>>>>I am using Inno Setup 5.2.3 to create a SETUP.EXE distibution disk of a VFP 9 application. I need to add VFPOLEDB to the distribution so that I can have an Excel Pivot Table connection read VFP free tables via OLEDB.
>>>>>
>>>>>I see that there exists a VFPOLEDB.MSM and VFPOLEDBSetup.MSI downloads on this site: http://www.microsoft.com/downloads/details.aspx?familyid=E1A87D8F-2D58-491F-A0FA-95A3289C5FD4&displaylang=en
>>>>>
>>>>>I am not sure the difference between the MSM vs the MSI files. Looks like the MSI is a Setup wizzard type installer while the MSM is a merge file.
>>>>>
>>>>>Can I use either the MSM or MSI file in conjunction with the Inno Setup process to supply and install this required component for end users? Anyone done this and if so could share the required steps for me to replicate it?