"Nevikski" <nevikski@tisconi.com> wrote in message
news:u8i%23TXRkGHA.4368@TK2MSFTNGP03.phx.gbl...
> Hi There
>
> We have a vs.2005 install which works fine, one of its jobs is to call a
> external app which in turn will fire the postgresql msi.
> This is where is fails, the postgre msi fires then stops because another
> install, (our first one) is still running. Question is how do we let the
> first intall complete before the second one starts?
>
> Thanks in advance
>
>

"Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message
news:%233wQnOWkGHA.4776@TK2MSFTNGP05.phx.gbl...
> People typically do this with a bootstrapper (or chainer that does each
> MSI in turn). The framework is MSI-based, so that has the same behavior,
> and you can solve it with a bootstrapper type of program that installs
> your MSI then the other one, if that's the order you want. You can use the
> MsiInstallProduct API or just use msiexec.exe /i <path to the msi>
> --
> Phil Wilson [MVP Windows Installer]
> ----
> "Nevikski" <nevikski@tisconi.com> wrote in message
> news:u8i%23TXRkGHA.4368@TK2MSFTNGP03.phx.gbl...
>> Hi There
>>
>> We have a vs.2005 install which works fine, one of its jobs is to call a
>> external app which in turn will fire the postgresql msi.
>> This is where is fails, the postgre msi fires then stops because another
>> install, (our first one) is still running. Question is how do we let the
>> first intall complete before the second one starts?
>>
>> Thanks in advance
>>
>>
>
>