> Hi Steve -
>
> Registering of OCXes usually requires privileges that "limited accounts" in Windows 2000 and XP, and any account in Vista with UAC, by default do not have, so the setup option is the easy one.
> See also Doug Hennig's article "Developing Microsoft Visual FoxPro Applications for Windows Vista" http://my.advisor.com/doc/18897
>
> If avoiding any setup is crucial, perhaps a "current user" approach might work (because HKLM assign requires admin privileges, while HKCU assign does not) which could be like:
> collect all required Registry values of your particular OCX, which are probably located in the HKLM branch (you can use SysInternal's RegMon tool to watch the regular setup).
> And at runtime, try to write them to the HKCU part, if not there yet. All required API functions are demonstrated in the registry.* libraries in the VFP Home() folder. See also Message ID: 195397 for an example.
>
> FWIW, MS "Virtual PC 2007" is free if you want to use virtual machines for testing.
>
>
> hth
> -Stefan

Thanks for the response.

One reason I was hoping to avoid setup.exe is that I have used Installshield Express in the past and always had a problem with 'updating' installed apps. I have been wanting to move to Inno but haven't had the time delve into it and and I was hoping to have something for others to test for me over the next few days. So I guess I have 3 choices, 1) Go back to using MSFT treeview, 2) Create setup, learning to use Inno - fwiw, I have seen link to tutorials so might give that a go or 3) implement what you mentioned above - which seems a lot of work just to avoid 1 or 2 :-)

Will think on it

Thanks again
Steve