Very Computer

Thanks

Tonie Venter

I hope this helps
Stuart

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.

Quote:> HI There
> I am including the MSDE merge modules in my setup
> application, and need to specify a Instance and Program
> Directory for the installation. I did find the
> Knowledgebase article on how to do this, but it is not
> completely clear on exacly where to set the Properties, is
> it in my own Project's properties, or is it in one of the
> merge module's property tables? I have tried to set it in
> my own project, but it does not have any effect. I have
> added it to the sqlbase.msm module, and also no effect. Is
> there anyone with advice on how to get this working?

> Thanks

> Tonie Venter

I have tried this method as well, but would like to use
the merge modules inside my own application to install. It
seems to be possible to use the merge modules as stated in
Microsoft Knowledge Base Article - 281983, and specify an
instance name, but I can not get this method to work. I am
not sure where to change the properties, if I change the
specified properties in my project, it does not influence
the MSDE setup. It still installs to the default
directory, and default instance. If it is not possible to
use the merge modules to install, i will revert back to
using the method using the setup.exe and setup.ini file.

Thanks

Tonie

Quote:>-----Original Message-----
>See Customizing Desktop Engine Setup.exe
>http://msdn.microsoft.com/library/default.asp?

Quote:>tsql_84xl.asp
>This contains syntax and arguments for customizing the

Customizable Installation Properties
The Setup.exe installation properties that can be changed using switches and
.ini file can also be changed in Windows Installer packages by editing the
Property table of the main .msi file. To edit the Property table, use a tool
such as Orca.exe, which is distributed as part of the Windows Installer SDK.
The properties that can be changed and the Setup.exe switches to which they
correspond are listed in the following table.

This information comes from the topic Using the SQL Server Desktop Engine
Merge Modules in the updated SQL Server 2000 Books Online which is now in
the MSDN Library, or can be downloaded from
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp.

--
Alan Brewer
Writer
SQL Server Documentation Team

I have added the SqlInstanceName Property in my setup.msi
file in the start of the install sequence, and it seems to
work when installing on a clean computer.....

When i run the MSDE setup.exe INSTANCENAME=ICAL, it starts
the installation process OK. Why is there a difference
when I define the variable in my setup.msi????

I suspect MSDE does the instance conflict checking before
the variable is set in my setup.msi file, How do I prevent
this?

Anyone with help on this?

Terrence

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.

Quote:> Thanks for the reply
> I used the example from the example.msi file, and it now
> installs and creates the correct instance when installing
> on a clean computer. The problem I am having now, is that
> it gives the error "The instance name specified is
> invalid" when i install it on a computer with a current
> installation of SQL Server 7. Why does it recognise and
> configure the instance correctly on a clean installation,
> but it does not work when there is an existing
> installation on the PC?

> I have added the SqlInstanceName Property in my setup.msi
> file in the start of the install sequence, and it seems to
> work when installing on a clean computer.....

> When i run the MSDE setup.exe INSTANCENAME=ICAL, it starts
> the installation process OK. Why is there a difference
> when I define the variable in my setup.msi????

> I suspect MSDE does the instance conflict checking before
> the variable is set in my setup.msi file, How do I prevent
> this?

> Anyone with help on this?