ICE17 checks for the situations shown in the example at the end of this topic.
Result
ICE17 displays an error or warning message for each of the situations in the example. Samples of such messages are shown in the following table.
| ICE17 error or warning | Description |
|---|---|
| PushButton: Button1 of Dialog: MyDialog does not have an event defined in the ControlEvent table.
Error |
There is a
Pushbutton control that is not listed in the
ControlEvent table.
If ICE17 returns this error on a PushButton for which the Enable Control attribute or the Visible Control attribute is not set in the Attributes column of the Control table, check whether the control also has an entry in the ControlCondition table. The control can unexpectedly become enabled, or visible, if the value in the Condition column changes to True, Enable, or Show. |
| Bitmap: Bitmap1 of Control: Bitmap1 of Dialog: MyDialog is not in the Binary table.
Error |
There is a Bitmap control or Icon control, but the corresponding bitmap or icon is not listed in the Binary table. Add the bitmap or icon to the Binary table. |
| RadioButtonGroup: RadioButton1 of Control: RadioButton1 of Dialog: MyDialog is not in the RadioButton table.
Warning |
There is a RadioButtonGroup control with values in the Property column and the Attribute column of the
Control table; the
Indirect bit is not set in the Attributes column. ICE17 posts a warning because the installer uses the property's value as a foreign key into the RadioButton table, but the value is missing from the primary key of that table.
If the Indirect bit is set, then the property listed for the control is not used as the property; instead, it is used as the name of the property that is actually used. This warning can be ignored if the control is created at runtime. For example, the ListBox control for on the FilesInUse Dialog is only created at runtime if there are files in use during the installation. |
| ListBox: ListBox1 of Control: ListBox1 of Dialog: MyDialog is not in the ListBox table.
Warning |
There is a
ListBox control with a value in the Property column of the
Control table and for which the
Indirect bit is not set in the Attributes column. ICE17 posts a warning because the installer uses the property's value as a foreign key into the
ListBox table, but the value is missing from the primary key of that table.
If the Indirect bit is set, the control changes the value of a property having a name that is the value of the property associated with this control. This warning can be ignored if the control is created at runtime. For example, the ListBox control for on the FilesInUse Dialog is only created at runtime if there are files in use during the installation. |
| ComboBox: ComboBox1 of Control: ComboBox1 of Dialog: ByDialog is not in the ComboBox table
Warning |
There is a
ComboBox control with a value in the Property column of the
Control table and for which the
Indirect bit is not set in the Attributes column. ICE17 posts a warning because the installer uses the property's value as a foreign key into the
ComboBox table, but the value is missing from the primary key of that table.
If the Indirect bit is set, the control changes the value of a property having a name that is the value of the property associated with this control. This warning can be ignored if the control is created at runtime. For example, the ListBox control for on the FilesInUse Dialog is only created at runtime if there are files in use during the installation. |
| ListView: ListView1 of Control: ListView1 of Dialog: MyDialog is not in the ListView table.
Warning |
There is a
ListView control with a value in the Property column of the
Control table and for which the
Indirect bit is not set in the Attributes column. ICE17 posts a warning because the installer uses the property's value as a foreign key into the
ListView table, but the value is missing from the primary key of that table.
If the Indirect bit is set, the control changes the value of a property having a name that is the value of the property associated with this control. This warning can be ignored if the control is created at runtime. For example, the ListBox control for on the FilesInUse Dialog is only created at runtime if there are files in use during the installation. |
| Bitmap: 'Bitmap2' for Control: 'Button2' of Dialog: 'MyDialog' not found in Binary table
Error |
There is a Pushbutton Control or Checkbox Control for which the Text column of the Control table does not contain a foreign key into the record of the Binary table containing the bitmap or icon. |
| Bitmap: 'Bitmap3' for Control: 'RadioButton2' of Dialog: 'MyDialog' not found in Binary table
or Icon: 'Icon1' for Control: 'RadioButton3' of Dialog: 'MyDialog' not found in Binary table Error |
There is a RadioButtonGroup control for which the Text column of the RadioButton table does not contain a foreign key into the record of the Binary table containing the bitmap or icon. |
| Picture control: 'Button3' of Dialog: 'MyDialog' has both the Icon and Bitmap attributes set
Error |
There is a PushButton, CheckBox, or RadioButtonGroup control with both the Icon bit or Bitmap bit set in the Attributes column of the Control table. You cannot set both attributes together. |
Example
Control Table (partial)
| Dialog_ | Control | Type | Attributes | Property | Text |
|---|---|---|---|---|---|
| MyDialog | Button1 | PushButton | 0 | OK | |
| MyDialog | Bitmap1 | Bitmap | 0 | Bitmap1 | |
| MyDialog | RadioButton1 | RadioButtonGroup | 0 | RadioButton1 | |
| MyDialog | ListBox1 | ListBox | 0 | ListBox1 | |
| MyDialog | ComboBox1 | ComboBox | 0 | ComboBox1 | |
| MyDialog | ListView1 | ListView | 0 | ListView1 | |
| MyDialog | Button2 | Pushbutton | 262144 | Bitmap2 | |
| MyDialog | RadioButton2 | RadioButtonGroup | 262144 | Property2 | |
| MyDialog | RadioButton3 | RadioButtonGroup | 524288 | Property3 | |
| MyDialog | Button3 | Pushbutton | 786432 | Ambiguous1 |
RadioButton Table (partial)
| Property_ | Order | Text |
|---|---|---|
| Property2 | 1 | Bitmap3 |
| Property3 | 2 | Icon1 |
The following tables are empty:
See Also
Send comments about this topic to Microsoft
Build date: 8/13/2009
© 2009 Microsoft Corporation. All rights reserved.