>>I used the setup wizard to create a network setup directory, to setup my application. I run the setup.exe off the network just fine, but when I ask my fellow programmer to run the setup.exe so as to test my code, she receives the following message:
>>
>>Setup could not open the file '\\402fs1\data2\vf\c40setup\netsetup\SETUP.EXE'
>>It is use by another application
>>
>>I have check permissions on the Network (Novell) and she has all she needs, basically the same as I. Has anyone seen the above error when running a network setup. I can run it with no problems, but she gets this everytime.
>>
>
>I've not seen that specific error, but I've gotten similar results when using a UNC reference to the SETUP with less than full access to the directory, especially where i relative relative references to files within my install (I've done a wide variety of things, including hacking the STF file to invoke custom procedures within the setup, or wrapping the VFP-generated Setup with a Wscript or InstallShield script to have things work the way I want them to, so I may have created some of my own problems.) Try having the other programmer map a drive letter at or above the level of the share, and then reference setup relative to the drive letter; it seems to cure a number of self-created ills, especially with nested scripts.

Thanks I will try that, it sounds like the setup wizard has a few bugs...