No replies so may be this is a bug. I have got around the problem by placing all my SQL scripts in a feature and set its condition so that it only gets ‘installed’ if the package is installed for the first time. ... View more

I have just encountered similar problem which I have not noticed before I use a pure MSI project. I run few SQL scripts during installation and one of them creates a database. I didn’t want the script to run during updates or repairs so I added a condition that includes “Not Installed”. As you can see below, the install releases that the script should only run during installation (Script Execution=RunOnInstall). --------------------------------------------------------------- Processing the SQL connection 'CreateLoggingDatabases'... Determining if there is at least one SQL script scheduled to execute under the connection... The SQL script 'Create_db_logging_SQLServer.sql' is not scheduled to execute. Script Execution=RunOnInstall, --------------------------------------------------------------- However, later on, it changes its mind and runs it destroying any existing data that exist in the database. --------------------------------------------------------------- Determining if the SQL script 'Create_db_logging_SQLServer.sql' will be executed... The SQL script will be executed because no schema version is found on the target database. Prepare executing SQL script file: 'Create_db_logging_SQLServer.sql'. Path: --------------------------------------------------------------- Is this an InstallShield or an MSI feature? ... View more

Either workaround would be helpful for now. Thank you for that. I hope this shortcoming is addressed in the next release or bug fix? ... View more

Sorry about the mix up of names in my earlier post. Of course I meant regedt32. The /s switch definitely works for me but it has to be specified before the .reg file name. Like: regedt32 /s trian_enu.reg ... View more

Thank you Michael for the reply. However, I wasn't asking if you can target more than one platform with a single MSI database. I am well aware that this is not possible. My question was about targeting more than one platform with a single InstallShield project. According to the help file this is possible. See "Targeting 64-Bit Operating Systems" : "Through the use of release flags, you can create one installation project for both 32-bit and 64-bit machines." I have done all that is necessary but I am unable to set the default target directory "INSTALLDIR" to what is required. Under 64 bit windows, users can install either the 32 bit or the 64 bit version of our software or both. If I specify [ProgramFilesFolder] in the INSTALLDIR product property, both version will install (by default) to "C:\Program Files (x86)\MyProgram". The biggest problem is that if I set the INSTALLDIR to "[ProgramFilesFolder]MyProgram", the 32 bit release builds OK but the 64 bit release produces lots of errors like the following: ISDEV : error ICE80: This 64BitComponent MyProgram.exe_x64 uses 32BitDirectory INSTALLDIR Component Directory MyProgram.exe_x64 If I set INSTALLDIR to [ProgramFiles64Folder]MyProgram, the 64 bit release build OK but the 32 bit produces the following sort of errors: ISDEV : error ICE80: This 32BitComponent MyProgram.exe uses 64BitDirectory INSTALLDIR Component Directory_ MyProgram.exe What I need is a way to set INSTALLDIR to [ProgramFiles64Folder] for the 64 bit version and [ProgramFilesFolder] for the 32 bit version. In other words, it should be possible to override the "INSTALLDIR" property in the release tab in a similar way to "Template Summary". Has anyone been able to target the 32 and 64 bit platforms with a single InstallShield project? May be there is another way to achieve this. ... View more

You can call regsvr32.exe directly passing in your .reg file and /s as arguments. Run the following command for full list of options: regsvr32 /? ... View more