>>No I dont make my own setup program. What I do is use the VFP Network setup to create its files out on our network (the cab files). I instruct the user to go to a certain drive adn directory where they will find the setup.exe. They run the setup.exe to have my application setup locally on their machine. Now when I fix any bugs or make enhancements I run the VFP setup to create the files on the network. The above code in my app check the network cab files and if they are more recent than the user exe my app comes up with a message box telling them to go to that drive and directory to reinstall their application. This way they dont run an old version.
>>
>>Hope this helps.
>
>AH...I see, said the blind man...however, here's my problem...going from your scenario above, when they go and run the new setup, it won't overwrite the program .exe on their machine, instead it just goes thru the motions and does not update anything.:( I'm using VFP 6, have you heard or seen this type of problem?

Yes I remember that problem now. I asked about it a long while back and received no help. I know it updates just about everything else, but the exe. At least it did in my tests. That left it for the user to uninstall and reinstall the application. Not good if your dealing with PC novices. You might give the setup wizard another try and this time tell it to setup a websetup. And point the files to be created somewhere on the network. Once the setup wizard gets done creating the web setup exe, go to it and double click on it. I think it will overwrite everything and do an install whether you had it previously installed or not. I dont know if this is a good solution, but it seemed the web setup overwrote the files where the network setup did not. Let me know if it helps.