Persistent variables across versions.

[marmadoc]

Hi!

My question is on persistent variables. Here is the scenario:

I previously built a package and saved the selected component states in persistent variables.

I am now modifying the script to perform an upgrade. Before I get to the component selection dialog I set up the selected components based on my persistent variables. This works fine for maintenance mode in the original installer, but I also need to do this now for normal installation since it is an upgrade and I only want to upgrade installed components.

The problem is that the persistent variables are undefined when I try to use them. This is after I make sure that this is an upgrade. I also try to retrieve the persisted variables before the previously installed version is removed.

So, I'm thinking that the persisted variables created in the initial install, is not available to this upgrade package because it has a new revision code.

So my questions are:
1. Are persisted variables stored per unique Product Code and Revision Code?
2. If this (1) is the case, is there a way to reference persisted variables from other versions based on the Product and Revision Codes?

Thanks!

[MichaelNesmith]

Try using the Save Feature Selections and Load Feature Selections commands.