Well, this could be a problem related to who I was logged in as. I'm just so used to being logged in as administrator, I sometimes forget that on a user's machine I don't have those rights. I'll have to go back and try it that way.

>>I'm hoping someone can shed some light on this.
>
>Same issue here, Fred. And some bad feedback from one customer yesterday on the quality of our installation routine! I just brought an application to them with an oldish "installshield Express" routine upgraded to new specific IExpress incarnation for VFP 9.
>
>On a recent severely secured win2K machine the whole installation (run as admin) ended up as a mess.
>
>In the end the win2K user(not admin) vfp-based exe was not able to reach the vfp*.dll dlls. Possibly because this corporate machine is highly-protected against hacking.
>
>The dlls both vfp* and additional dll and ocx (installed under admin user name) were set into the windows system32 dir. Was it the right thing to do or is it now a bad habit that should be changed?
>
>I'd be glad to read some definitive input on:
>- were should dll (both vfp* and others resources - OCXs and others) be? I expect possibly in an application-level directory?
>- how are the vfp-generated executables made aware of dlls when installed outside windows system32 directory,
>- is "installshield Express for VFP 9" able to cope with such installs?
>
>Thanks for any feedback, tip or trick
>
>Franck