Another possibility is to send SQL Scripts. For the first installation this
is not the easiest, but as you start to make changes to the database (which
you will probably have to do since no one is perfect (hopefully a certain Mr
Celko isn't listening :) ) you will have to do this going forward so as not
to kill their data when you make changes. If you have no bugs whatsoever,
you will have to make changes because they will love you so much they will
want more out of you :) Then they create the database, and they run the
scripts (you should probably have the scripts loaded by a CMD file that
launches OSQL or SQLCMD for them, unless they are DB savvy and want to run
their own scripts)
--
----------------------------------------------------------------------------
Louis Davidson -
http://spaces.msn.com/members/drsql/ SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
[quoted text, click to view] "James_101" <James101@discussions.microsoft.com> wrote in message
news:4CA74928-7837-4A7A-8D0E-DD473114428E@microsoft.com...
>I design computer-based training that stores user scores in a database.
>The
> training software sends the data to ASP pages that send the data on to the
> database. Because of a large client, I am using SQL Server rather than
> Microsoft Access for the db.
>
> I have designed and tested the db using the Developer's Edition for SQL
> Server 2000. Now, I need to send the database to my customer who will
> install it on a db server which uses SQL Server. What files should I send
> to
> the customer?
>
> Thanks.
