I had tried IS a year back and chances are very high that I might have distributed the DLL. right now I have settled with the idea of using a special MSI containing MSM for VFP, ODBC and basic OCXs required by me. Currently I plan to use Inno for Applications only until I gain more experience with it.

Thanks for all the replies, your responses have been very helpful. In fact I guess my experience with Inno might have failed if it hadn't been for the initial script you had provided.

>>I have been scared that if these mscomctl.ocx don't gell with the users machine all hell can break loose. I have s W2K machine and generally clients have W98 machines. I had a long time ago (maybe it was me as I was a newbie) distributed the mscomctl.ocx from W2K to a W98 machine and I ended up reinstalling W98 on that machine.
>>
>>Please clarify my doubts, why they say so, that mscomctl.ocx is not to be distributed but the installation should point to the MS link so that the client can DL the most compatible version, blah, blah, blah.
>
>Maybe you're thinking of comctl32.dll? The Inno Setup documentation has a page about "unsafe files" that makes this point about comctl32.dll. It also mentions two other files to be careful with, but mscomctl.ocx is not one of them. AFAIK there are no issues concerning the distibution of mscomctl.ocx on different platforms, but if you have had experience to the contrary then you should seek more information before proceeding.
>
>>Inno is great I am learning and appreciating it.
>
>I agree, Inno Setup is a very nice tool.