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.

Inno is great I am learning and appreciating it.

>>>The Inno Setup 'regserver' flag should be equivalent to registering the control manually with RegSvr32. Can you successfully register the control from the command line on the target machine using RegSvr32? If not, see the 'Installation Notes' section of the bbListView help file - maybe a required file is missing on the target machine.
>>
>>I browsed through the news archives and found that the .PLB which accompanies the OCX need to be registered and I guess that solved the problem. Appreciate your help.
>>
>>Any advise for TreeView distribution?
>
>If you're deploying a VFP 6 app you can redistribute MSCOMCTL.OCX, which contains the treeview control. In your Inno Setup script, install it as follows:

[Files]
>Source: \winnt\system32\mscomctl.ocx; DestDir: {sys}; Flags: regserver sharedfile restartreplace