"Ali" <ali.saifee[ at ]gmail.com> wrote in message
news:cd471aa7-717a-478e-a3cb-f0d3b2b65d7f[ at ]w1g2000prk.googlegroups.com...
[Quoted Text] > I have an installer from a previous build that was installed on a non
> english machine (the language of the base product is english, and i
> have transforms for each language (which moreover only transform the
> UI strings).
> When i install a minor upgrade i get an error -2229. Digging into the
> log results in the following error line:
> DEBUG: Error 2229: Database: . Could not load table 'Control' in SQL
> query: SELECT `Control`, `Type`, `X`, `Y`, `Width`, `Height`,
> `Attributes`, `Property`, `Text`, `Control_Next`, `Help` FROM
> `Control` WHERE `Dialog_`=?
> Between the two revisions that were being upgraded, I had added a new
> dialog into the installer UI sequence. However, this same scenario
> does *not* fail if the initial installation was in English.
> Is there some kind of rule for minor upgrades that new dialogs or
> changes in the InstallUISequence are not permitted (only for
> transforms?)
Likely when you add your new UI the corresponding non-english MSTs are also
updated to ensure all the new UI works in those languages. However once
transforms are applied they are permanent so you are left using the old
language transform with new base MSI (or combination of original MSI + new
transform changes from the MSP + the original non-english MST itself).
Regardless the combinations leave you in a position where your new UI
changes will have to workaround the old transform OR you need to move to
full major upgrade so that you can use the new language transforms instead.
Try to apply the old non-english language transform directly on top of your
new upgraded MSI file. You could use a newer Orca version to help with
this. You will likely find some problems in trying to get it to apply but if
not do a full validation to see if there are any errors introduced by the
new MSI when using the old language transform.
Sincerely,
Adrian Accinelli
|