try looking at:
http://www.microsoft.com/sql/techinfo/development/2000/MSDE2000.asp

You need to invest in one of these: Visual Studio .NET, Visual Studio 6, any
version 6 develoopmental language, Access 2000, Office Pro, or SQL Server,
or Windows XP pro  then you get MSDE as a bonus on the installation kits.
In most cases you have the right to redistribute the MSDE installation kits
royality free.  This seems like a any of these are reasonable ways to obtain
what you need -- just look for the MSDE*.* and you will find it.  The Visual
Studio 6 version is SQL 7 compatible whereas the Visual Studio.NET,
Access2000, and Windows XP version is SQL2000 compatible -- they apparently
do not co-exist....

Have fun.



----- Original Message -----
From: "Seth Bembeneck" <sbembeneck@c...>
To: "pro_VB_dotnet" <pro_vb_dotnet@p...>
Sent: Friday, May 10, 2002 6:18 AM
Subject: [pro_vb_dotnet] Re: Creating Database


> Where can I download MSDE?
>
> Seth
>
>
>
> > MSDE is the "personal" SQL Server.  It is free.  You get it when you
> install
> Visual Studio or Access 2000 or uou can download it separately from
> Microsoft.  Visual Studio.NET also has utilities to help you manage
> tables,
> indexes, stored procedures, etc.  If you ask for a free 60 day trial
> version
> of MS SQL 2000 you also get it.  The free 60 day trial of MS SQL 2000 also
> includes enterprise manager which I especially like.  You can install the
> server utilities without installing the MS SQL itself and then you can use
> Enterprise Manager and Query Analyzer to manage your MSDE.  Also note that
> if you are working at a workstation (as opposed to WIN2000 Server) you are
> likely to have the full MS SQL package only install the personal edition
> (MSDE) on your workstation.
>
> MSDE takes up about 60 Megabytes of RAM.  Take care to install it on a
> machine with 250 MB RAM or more -- then you will have sufficient RAM for
> that, Visual Studio.NET and the several other apps you are likely to keep
> running at the same time.
>
>
>
>
>
> ----- Original Message -----
> From: "Seth Bembeneck" <sbembeneck@c...>
> To: "pro_VB_dotnet" <pro_vb_dotnet@p...>
> Sent: Wednesday, May 08, 2002 6:04 AM
> Subject: [pro_vb_dotnet] Re: Creating Database
>
>
> > Thanks. Do you need an SQL Server to use sql commands? If so, do you
> know
> > of any servers that are free?
> > Seth
> >
> >
> >
> >
> > > SQL to insert one row is:   INSERT INTO table_name
> > (Comma_delimited_field_list) Values (Values in a comma delimited list)
> >
> > SQL to create the tabe is:   something like this one:
> >
> > CREATE TABLE [OrderItems] (
> >  [OrderId] [int] NOT NULL ,
> >  [ItemId] [int] NOT NULL ,
> >  [UnitPrice] [money] NOT NULL ,
> >  [Quantity] [int] NOT NULL
> >
> > SQL to create an index looks like this:
> > CREATE  INDEX [ixTransactionDetailsOrderId] ON [OrderItems]([OrderId])
> >
> > -OR- create the complete Db in access and do not insert any but the bare
> > minimum of records - mark the *.mdb as a read only file.  Copy that file
> > to
> > your distribution files.  When ready to setup, copy that file to the
> file
> > name of he database you intend to use.  Also be aware that these files
> Zip
> > really well. So you might want to establish a database ready to startup
> > then
> > zip it up.  To install in this case is just unzip it.  Zip typically
> > compresses Access down to something in the order of 10% of its original
> > size, so this is a very practical distribution method.
> >
> > If you need to make database changes after the client sets up his/her
> > database then you need to use the ALTER TABLE [table_name]  style sql
> > commands.  OR, you could compose a new database file and write custom
> SQL
> > to
> > move data from the old databae into the new one.  I like the latter
> > because
> > if something goes wrong there is a better chance that I can find the
> > original data untouched (never assume a client backedup anything). And,
> > if i
> > get stuck "fixing" the problem, I can keep hammering away at the problem
> > until no problem exists.
> >
> > Another approach that you can use with ADO.NET is worthy of your
> > consideration as well.  You can export an XML file either either just
> the
> > table schema (structure), or with schema and data.  Then you can use
> > ADO.NET
> > to read the XML file and to make a recordset from it. Update the
> database
> > as
> > you normally do in ADO.NET.   I have not tried to create a database this
> > way, but it may be possible.  I have used this technique to load data.
> > This
> > is less compressed than the database itself, and because it is ASCII
> text,
> > your client may be tempted to open it in a text editor with totally
> > unknown
> > and potentially dangerous consequences to you.
> >
> >
> > Hope this helps.  If you are new to SQL, take some time to learn the
> basic
> > SQL operations.
> >
> >
> >
> > ----- Original Message -----
> > From: "Seth Bembeneck" <sbembeneck@c...>
> > To: "pro_VB_dotnet" <pro_vb_dotnet@p...>
> > Sent: Friday, May 03, 2002 9:00 PM
> > Subject: [pro_vb_dotnet] Creating Database
> >
> >
> > > I have created an Access database connection, creating a new database
> at
> > > the same time. How do I add tables? If I'm going about doing this the
> > > wrong way, How do I create an Access database and add tables to it?
> > > Seth Bembeneck
> >
>