This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- SQL Script conditions are not work while Minor Upgrade
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 21, 2008
10:11 AM
SQL Script conditions are not work while Minor Upgrade
Hi,
I need to avoid SQL script execution while minor upgrade. I set the following condition for in Conditional Statement of Runtime tab for SQL script: Not IS_MINOR_UPGRADE, but SQL script is executed because Component State=Install
I even tried to set certainly failed condition like 1<>1 but component state was still Install!
I have also tried to use IS_SQLSERVER_CXNS_ABSENT_FROM_INSTALL and set connection name to skip, but as Conditional Statement, this works only at install mode and doesn’t work at maintenance mode.
Is this is bug? If there any workaround for this bug?
I need to avoid SQL script execution while minor upgrade. I set the following condition for in Conditional Statement of Runtime tab for SQL script: Not IS_MINOR_UPGRADE, but SQL script is executed because Component State=Install
I even tried to set certainly failed condition like 1<>1 but component state was still Install!
I have also tried to use IS_SQLSERVER_CXNS_ABSENT_FROM_INSTALL and set connection name to skip, but as Conditional Statement, this works only at install mode and doesn’t work at maintenance mode.
Is this is bug? If there any workaround for this bug?
(2) Replies
![](/skins/images/19F9C6DC056868BD0EEB3511534AB4E7/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 21, 2008
11:02 AM
SQL Scripts use component conditions during installation and as such are subject to those rules. Specifically, this section involving the Condition column of that table is relevant:
http://msdn2.microsoft.com/en-us/library/aa368007(VS.85).aspx
This column contains a conditional statement that can control whether a component is installed. If the condition is null or evaluates to true, then the component is enabled. If the condition evaluates to False, then the component is disabled and is not installed.
The Condition field enables or disables a component only during the CostFinalize action. To enable or disable a component after CostFinalize, you must use a custom action or the DoAction ControlEvent to call MsiSetComponentState.
Note that unless the Transitive bit in the Attributes column is set for a component, the component remains enabled once installed even if the conditional statement in the Condition column later evaluates to False on a subsequent maintenance installation of the product.
The Condition column in the Component table accepts conditional expressions containing references to the installed states of features and components. For information on the syntax of conditional statements, see Conditional Statement Syntax.
http://msdn2.microsoft.com/en-us/library/aa368007(VS.85).aspx
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 21, 2008
03:58 PM
Thank you very much!
I have resolved the problem with Transitive bit.
I have resolved the problem with Transitive bit.
![](/skins/images/19F9C6DC056868BD0EEB3511534AB4E7/responsive_peak/images/icon_anonymous_message.png)