Mike,

Windows Installer, the underlying technology employed by setups built with InstallShield Express, uses a set of rules to determine whether to replace an existing file while installing an update. These rules are documented in the Windows Installer Help file that comes with InstallShield Express. For versioned file, like EXE files, the version number is important. In general you should incremement the version number of your app's EXE file for each update you distribute. If an upgrade package is not replacing an existing EXE file on the target machine that'd be the first thing I'd check.

-Rick

>I have been working with INSTALL SHIELD EXPRESS 3.5 SP 4 that comes with VFP 8.0 and have it working and am pretty happy with it now that I have got through its rather geeky Help Files.
>
>But I find now that I am using it to build upgrades that it is not working so well. I had a problem upgrading one customer and went back to my lab and found that the date of the .EXE file that it was installing was not the same as the date of the .EXE that I used in the Build.
>
>I have done the build twice and installed from the SETUP.EXE that it built and found that each time it did not update the EXE file at the Target Directory.
>
>I contacted Install Shield and they want me to a) sign a service contact before they will investigate and b) upgrade to their latest version which I think is now 10.5.
>
>One thing I have noticed about the Builder is that it seems to be unable to build new files to the original upgrade folder. It says the folder has no write privileges (even though Read Only is unchecked). So I have to delete the previous folder and let it build a new folder each time. I don't know if this a factor.
>
>If anyone knows how to deal with the type of problem I am experiencing, I would be pleased to hear from you.
>
>Mike Smith