Yes, that worked.
Now I'm being asked why 3 other (and older) installers that are still being built with 12.3.1 work when we only change the 4th-place version number and generate a new Product Code? I assumed it was the different Product Code.
We have an automated build system that runs several times a day. Each build increments a build number for the 4th-place and generates new Product Codes. This way each build can upgrade any previous build. We've been operating this way for a long time.
But this new installer I'm working on, based on 12.7.2, behaves differently. I had it setup identically to the older ones - but it won't trigger upgrade behavior.
So I'm being asked "What changed?".
* Is it a change in Advanced Installer?
* A fix to a quirk that we have been taking advantage of?
* A change to Windows Installer?
* What?
The problem is we would have to change how we handle version numbers in our company and with our customers. So they would like an explanation as to why.
Thanks again for your time and effort. I have send your support another Zip with this new 12.7.2 project and an older 12.3.1 project titled "Upgrade confusion" for comparison

FOLLOW US
Get the latest news in Application Packaging