Software Deployment

Hi all,

I'm a regular visitor to the site and have received many a helpful answer over the past couple of years, without actually needing to post myself, but despite several hours' searching I'm unable to find an answer to my specific situation - if there is one, I apologise. Hence this is my first post..

We have an in-house developed product which was packaged using Wise Package Studio by my predecessor. Since he left it has come to light that a particular component is being installed incorrectly. I've corrected this by opening his existing WSI project file and making the necessary changes, then rebuilding the MSI. The Product Version remains the same, as does the Upgrade Code, however Wise has given the package a new Product Code presumably due to the removal of a component and addition of a new one.

I have set up the Upgrade table with the following values;

Upgrade Code: (The upgrade code of both packages)
VersionMin: 8.5 (the version of both packages, new & old)
VersionMax: 8.5
Language: 1033
Attributes: <0x304> (Include min & max versions, ignore failure to remove)
Remove: <null>
ActionProperty: UPGRADE_1 (Which is in the SecureCustomProperties property)

My goal is to be able to roll out this new package to machines whether the existing package is present or not, however where present Windows Installer is insisting that a newer version is already installed, despite setting up the Upgrade table to include this product version.

I'm obviously doing something wrong, however I can't figure out what it is. I've tried many permutations of Upgrade attributes to no avail. Any help / advice would be greatly appreciated.

Thanks in advance.