I was able to create an install using AI 7.6.1 using the Multiple Instance functionailty to support up to 40 instances of my application. It works great, and I love being able to manage the installed instances independently. Naturally, I needed to be able to create and apply updates and patches to any previously installed instances as well as install new instances of a more recent version of my application alongside older instances that were previously installed. I ran into an interesting problem.
In my case, I installed 3 instances of my original build. I'll call them B1, B2 & B3. I then bumped up the Product Version and said "No" to generating a new Product Code. When I run the new build, I get the choice of whether to manage one of my 3 previous installs or to create a new instance. If I attempt to install a new instance, it acts as though it's going to do so, and then the installer simply goes away. Log files says it installed the new instance, but it didn't do anything.
So, I decided to experiment and see what happens if I upgrade one of the previously installed instances. I chose to upgrade the B2 instance, and it worked fine. I then attempted to create a new instance with the newer installer, and got the same results. So, I upgraded B1 this time. Then I attempted to install a new instance and it worked. So I ended up with my B1 and B2 instances being updated, a new B4 instance, and an old B3 instance installed. So it seems that I was not able to create a new instance of the updated install until I at least upgraded my base instance first.
Is there a way to fix this behavior so that I am not required to update the base instance prior to being able to install a new instance of a more recent install package?
Thanks in advance,