Deploying MSDE200 w/ app

I need to deploy my msde2000 database with an application
using Wise Install. If you've done this before, do you
have any documentation or procedures to set this up? I
would greatly appreciate any help on this.
Thanks in advance,
George
greda@.msn.com
Thanks for your help. I'll check out the links.
George

>--Original Message--
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/dnmsde/html/msdedepl.asp
>Check out that website, it has a tutorial on using MS'
MSDE Bootstrapper. This site has useful info on how to
actually tap into the app's installation events and
script a database/drop a database. I personally used a
bootstrap program I found here:
>http://www.codeproject.com/dotnet/dotNetInstaller.asp?
target=dotNetInstaller
>I could never figure out exactly how to use the
Microsoft MSDE Bootstrapper, very very poorly documented,
while the example on how to use it was decent, it seemed
it was skirting past the basics, like instructing whether
the MSDE path you specify is to the correct .MSI, or
Setup.EXE, or whether it worked against MSDE2000 release
A or not, and it never pointed out how to set a
bootstrapper in a projects configuration. Really poor
documentation, I'm sure it's great if you know exactly
how the heck it works. I can't get past that, so some
Italian kid sold me on his bootstrapper, which for
usability and flexibility, it far surpasses the Microsoft
MSDE Bootstrapper.
>My 2 cents.
>.
>
|||Thanks for your help Jim. I'll follow your instructions.
if you have any sample code I can look at, that would
help me tremendously. Its my first time deploying a
product using MSDE2000. I'm wondering how you would
handle multiple users? One CD with MSDE2000 and another
with the client software?
Thanks. George

>--Original Message--
>I've had to do exactly what you are try to accomplish.
>Our company produces and distributes a MSDE based
client - server
>application and we use Wise for the installation
platform. The installation
>process is separated into three stages: 1) Install MSDE
2) Install our
>database and configure users and permissions 3) Install
the application.
>Here's a brief description of what we do.
>For Stage 1 I developed a Wise scritp for installing
MSDE using the MSDE
>setup.exe program. I gather all the need parameters from
the installing user
>and then bootstrap
>setup.exe, install a named instance of MSDE, and wait
for it to exit. I
>examine the return value from the process to see if the
installation
>succeded. If it did I then put a value in the registry
to have the next
>stage of the installation run automatically when the
system reboots. I then
>force a reboot of the system. I make no attempt to try
to make the
>installation of MSDE seamless or not require a reboot,
as most times a
>reboot is required before SQL Server will run. For
Windows 9x systems I then
>install a small executable that runs at boot time and
that will start up SQL
>Server (there are no services in Win9x), rather than
trying to configure
>something in the Startup folder.
>Stage 2 - In my next Wise script I look for my named
instance of MSDE. I've
>written a helper DLL that uses SQL-DMO and T-SQL to
provide a number of
>needed functions for doing preliminary database
configuration such as
>searching for runnning instances of SQL Server,
attaching the database,
>creating logins and such. If I find my instance then I
connect to it using
>the sa account, copy the database from the installation
source to the data
>directory of MSDE and attach it. I then create the
needed logins for the
>application. This current application uses ODBC (the
next version will use
>ADO) so I then create an system ODBC connection for the
application. To do
>this I run the user through the ODBC wizard (Wise can
fire this off for you)
>so that the user can determine that the connection is
valid and works.
>Stage 3 - Install the client application. This is a just
a straight forward
>application installation.
>Our product is installed on hundred of systems and the
installation process[vbcol=seagreen]
>has a very low failure or problem rate.
>Jim
>"George" <greda@.msn.com> wrote in message
>news:1912001c44ca9$e6dc0760$a301280a@.phx.gbl...
application
>
>.
>