If the user no longer pays for a certain 'data' file, it should be removed with the next deployed iteration of our software. A different registration code is issued to reflect this change.
Initially, the certain component was marked as Reevaluate Condition and my install seemed to do what it was supposed to. The file no longer existed based on the condition that was reevaluated with information from the newly issued registration code.
My problem arose when I learned of the problem concerning components not being properly installed conditionally on 95 & 98 systems. It seems now that I have embedded some of the data file components in sub-features (so they would install properly based on conditions on 95 & 98 machines) The reevaluate condition function no longer works as it initially did.
Is there a work around or is this a known problem?
All help GREATLY Appreciated!!!