MSDE merge modules

Hi
I wonder if anyone can help. I am looking for the MSDE merge modules to use
in a .net 2003 set up and deployment module. see
http://support.microsoft.com/kb/325004/EN-US/
However I have already installed SQL server standard edition on my
development server. How do I get these MSM's to merge into my MSI? Am I
barking up the wrong tree?
Thanking you in advance for any help
Richard
Hello,
Personally, I use the last setup of msde (sql2000.msi and I launch it
from my setup with a custom action.)
With that, I don't need to use the merge modules and if a custommer want
to use SQL Server instead, I don't need to change my setup (I don't need
to install MSDE and just connect to sql server and it will work.)
I can give all the parameters to msiexec (or to the property table of
the msi).
Marc Allard
Allcomp
Richard Wilde wrote:
> Hi
> I wonder if anyone can help. I am looking for the MSDE merge modules to use
> in a .net 2003 set up and deployment module. see
> http://support.microsoft.com/kb/325004/EN-US/
> However I have already installed SQL server standard edition on my
> development server. How do I get these MSM's to merge into my MSI? Am I
> barking up the wrong tree?
> Thanking you in advance for any help
> Richard
>
|||Hi
I am interested in how you do this. You suggest that you can supply the
paramters to msiexec or the property table of MSI? Please can you point me
in the right direction.
After the instance has been created how do you then create the database and
insert any data?
Thank you for your help so far.
Richard
"Allcomp" <marc@.nospam.allcomp.be> wrote in message
news:41e4d0e0$0$329$ba620e4c@.news.skynet.be...[vbcol=seagreen]
> Hello,
> Personally, I use the last setup of msde (sql2000.msi and I launch it from
> my setup with a custom action.)
> With that, I don't need to use the merge modules and if a custommer want
> to use SQL Server instead, I don't need to change my setup (I don't need
> to install MSDE and just connect to sql server and it will work.)
> I can give all the parameters to msiexec (or to the property table of the
> msi).
> Marc Allard
> Allcomp
> Richard Wilde wrote:
|||Hello,
Here is how I do that ...
1) Create a
property MSIExecPos
Value : msiexec
in the table property of the msi file (or the merge module)
2) Create a custom action
InstallMsde
Type : 114 (to ignore the return code because in Win98 sometimes the
return code is not 0 so you have problems).
source : MsiExecPos
Target
/i "MSDE\Sql2000.msi" /qb /l c:\msde.log
Personally, I put the full MSDE installation directory into a sub
directory MSDE so the root of my CD is cleaner
3) In the InstallUISequence (you have tu use InstallUISequence or the
installation won't work)
You add the action
InstallMsde
You can put a install condition or not
For the sequence, you put something in the end (1305 in my case).
After that, you can change the parameters of the MSDE file
In the property table, you put
REBOOT Value : ReallySuppress
to avoid a reboot prompt after the installation of MSDE
INSTANCENAME value : NameofYourInstance
I believe that it is necessary because if a custommer has already MSDE
installed, then you will run into very big problems to install your software
DISABLENETWORKPROTOCOLSValue : 0
If you don't do it, your server will only work locally.
SqlSaPwdValue : YourPassword
I think it is better to pass it directly in the custom action instead of
the property table.
Normally with that, all should be fine
Marc Allard
Allcomp
Richard Wilde wrote:
> Hi
> I am interested in how you do this. You suggest that you can supply the
> paramters to msiexec or the property table of MSI? Please can you point me
> in the right direction.
> After the instance has been created how do you then create the database and
> insert any data?
> Thank you for your help so far.
> Richard
> "Allcomp" <marc@.nospam.allcomp.be> wrote in message
> news:41e4d0e0$0$329$ba620e4c@.news.skynet.be...
>
>