SQL Express or MDB - opinions please

[Miro]

Ok I have been slowely - and ever so slowely teaching myself VB.net

Currently I have created an MDB file by code, and added fields to the MDB
file by code.
I like this solution because, ( im assuming ) if I create an EXE and I load
an MDB file, I can
see if certain fields are there, and if not add them.
Kinda like an Update that is imbeded into the EXE, so you dont always have
to create an Install shield.

So... Lets say my goal is to have an application that I would like people to
install somewhere.
Why choose SQL Express over a simple MDB file? ( i have never tried SQL
Express )

1. As I am assuming...SQL express is a second install that a user would
have to install ontop of my
application install ?

2. MDB files would be easier to work with because everyone till now has
been working with
MDB files so any help required is easier to get to ?

3. People have told me MDB files will slowely be processed out and SQL
Express will take its place.
Is this true ?

So if you were to write an application from scratch. Would you still go
with SQL Express ?

I am knocking my head back and forth on this. And would like to know how i
will create my db's before i start
trying to code an app.

Thank You,

Miro

[Cor Ligthert [MVP]]

Miro,

In the newsgroup general and adonet is this often asked.

See here one thread of those, it gives you direct the entree to more if you
want.

http://groups.google.com/group/micro...1eca691cf65511

I hope you get an idea by this discussion.

Cor
"Miro" <mi******@golden.net> schreef in bericht
news:eh**************@TK2MSFTNGP05.phx.gbl...

Ok I have been slowely - and ever so slowely teaching myself VB.net

Currently I have created an MDB file by code, and added fields to the MDB
file by code.
I like this solution because, ( im assuming ) if I create an EXE and I
load an MDB file, I can
see if certain fields are there, and if not add them.
Kinda like an Update that is imbeded into the EXE, so you dont always have
to create an Install shield.

So... Lets say my goal is to have an application that I would like people
to install somewhere.
Why choose SQL Express over a simple MDB file? ( i have never tried SQL
Express )

1. As I am assuming...SQL express is a second install that a user would
have to install ontop of my
application install ?

2. MDB files would be easier to work with because everyone till now has
been working with
MDB files so any help required is easier to get to ?

3. People have told me MDB files will slowely be processed out and SQL
Express will take its place.
Is this true ?

So if you were to write an application from scratch. Would you still go
with SQL Express ?

I am knocking my head back and forth on this. And would like to know how
i will create my db's before i start
trying to code an app.

Thank You,

Miro

[Miro]

Thank you Cor,

That is what I needed.

A good read for everyone who is thinking the same thing.

I personally will try now to install SQL Server and see what happens from
here, or how hard it is to learn :)

Thank you again.

Miro

"Cor Ligthert [MVP]" <no************@planet.nl> wrote in message
news:uy**************@TK2MSFTNGP04.phx.gbl...

Miro,

In the newsgroup general and adonet is this often asked.

See here one thread of those, it gives you direct the entree to more if
you want.

http://groups.google.com/group/micro...1eca691cf65511

I hope you get an idea by this discussion.

Cor
"Miro" <mi******@golden.net> schreef in bericht
news:eh**************@TK2MSFTNGP05.phx.gbl...

Ok I have been slowely - and ever so slowely teaching myself VB.net

Currently I have created an MDB file by code, and added fields to the MDB
file by code.
I like this solution because, ( im assuming ) if I create an EXE and I
load an MDB file, I can
see if certain fields are there, and if not add them.
Kinda like an Update that is imbeded into the EXE, so you dont always
have to create an Install shield.

So... Lets say my goal is to have an application that I would like people
to install somewhere.
Why choose SQL Express over a simple MDB file? ( i have never tried SQL
Express )

1. As I am assuming...SQL express is a second install that a user would
have to install ontop of my
application install ?

2. MDB files would be easier to work with because everyone till now has
been working with
MDB files so any help required is easier to get to ?

3. People have told me MDB files will slowely be processed out and SQL
Express will take its place.
Is this true ?

So if you were to write an application from scratch. Would you still go
with SQL Express ?

I am knocking my head back and forth on this. And would like to know how
i will create my db's before i start
trying to code an app.

Thank You,

Miro

[Michel Posseth [MCP]]

> 1. As I am assuming...SQL express is a second install that a user would

have to install ontop of my
application install ?
well a lot of people nowadays have a sql express or MSDE instance running
without even knowing it
2. MDB files would be easier to work with because everyone till now has
been working with
MDB files so any help required is easier to get to ?
if you know for sure all people have Jet oledb installed ( this is not
standard annymore in MDAC since version 2.6 )
okay having office installed will also work :-)
3. People have told me MDB files will slowely be processed out and SQL
Express will take its place.
Is this true ?
In my opinion yes , you could also go for the firebird DB engine wich has
a verry nice .Net API is completely free ( without anny restrictions , and
has even an embedded version ) http://firebird.sourceforge.net/ however
it is not as "friendly" to start with as MSSQL

So if you were to write an application from scratch. Would you still go
with SQL Express ?
This depends on the project for me .

Why would i choose Access ( i prefer the 2000 db ) above sql express
1. small ( i should say smaller ) footprint
2.deployable to all Windows versions inclusive win 9.x
3. security and then i mean the possibility to secure so no one else except
you can access the database
while still having the posibility to use indexes etc etc on the data (
this is done with a workgroup information file , using this technique you
can add user roles and encrypt the database )

by the way i believe the best database there is at this moment is MS SQL
2005 ( SQL Express ) it is only a shame that they forgot that even a
administrator of a system should be restricted access from a db from a
programmers point of view in some situations

Hope to have given you some ideas

regards

Michel Posseth [MCP]

"Miro" <mi******@golden.net> schreef in bericht
news:eh**************@TK2MSFTNGP05.phx.gbl... Ok I have been slowely - and ever so slowely teaching myself VB.net

Currently I have created an MDB file by code, and added fields to the MDB
file by code.
I like this solution because, ( im assuming ) if I create an EXE and I
load an MDB file, I can
see if certain fields are there, and if not add them.
Kinda like an Update that is imbeded into the EXE, so you dont always have
to create an Install shield.

So... Lets say my goal is to have an application that I would like people
to install somewhere.
Why choose SQL Express over a simple MDB file? ( i have never tried SQL
Express )

1. As I am assuming...SQL express is a second install that a user would
have to install ontop of my
application install ?

2. MDB files would be easier to work with because everyone till now has
been working with
MDB files so any help required is easier to get to ?

3. People have told me MDB files will slowely be processed out and SQL
Express will take its place.
Is this true ?

So if you were to write an application from scratch. Would you still go
with SQL Express ?

I am knocking my head back and forth on this. And would like to know how
i will create my db's before i start
trying to code an app.

Thank You,

Miro

[Cor Ligthert [MVP]]

> it is only a shame that they forgot that even a administrator of a system

should be restricted access from a db from a programmers point of view in
some situations

LOL

[raibeart]

I think you have it backwards from the Administrator's point of view.

Programmers should always be restricted.
Michel Posseth [MCP] wrote:

2005 ( SQL Express ) it is only a shame that they forgot that even a
administrator of a system should be restricted access from a db from a
programmers point of view in some situations

[dbahooker]

mdb is crap.

spit on anyone that uses it or tells you to use it.

sql server 2005 express friggin rocks!!!

-Aaron
raibeart wrote:

I think you have it backwards from the Administrator's point of view.

Programmers should always be restricted.
Michel Posseth [MCP] wrote:

2005 ( SQL Express ) it is only a shame that they forgot that even a
administrator of a system should be restricted access from a db from a
programmers point of view in some situations

[Dennis]

If I read your comment correctly, if I have MSDE installed, then I can
install an application that uses SQL Express...is this correct? Also, is
MSDE installed with Windows XP Professional automatically? Thanks for any
info you can provide as I am considering switching to SQL Express.
--
Dennis in Houston
"Michel Posseth [MCP]" wrote:

1. As I am assuming...SQL express is a second install that a user would
have to install ontop of my
application install ?

well a lot of people nowadays have a sql express or MSDE instance running
without even knowing it

2. MDB files would be easier to work with because everyone till now has
been working with
MDB files so any help required is easier to get to ?

if you know for sure all people have Jet oledb installed ( this is not
standard annymore in MDAC since version 2.6 )
okay having office installed will also work :-)

> 3. People have told me MDB files will slowely be processed out and SQL
Express will take its place.
Is this true ?

In my opinion yes , you could also go for the firebird DB engine wich has
a verry nice .Net API is completely free ( without anny restrictions , and
has even an embedded version ) http://firebird.sourceforge.net/ however
it is not as "friendly" to start with as MSSQL

So if you were to write an application from scratch. Would you still go
with SQL Express ?

This depends on the project for me .

Why would i choose Access ( i prefer the 2000 db ) above sql express
1. small ( i should say smaller ) footprint
2.deployable to all Windows versions inclusive win 9.x
3. security and then i mean the possibility to secure so no one else except
you can access the database
while still having the posibility to use indexes etc etc on the data (
this is done with a workgroup information file , using this technique you
can add user roles and encrypt the database )

by the way i believe the best database there is at this moment is MS SQL
2005 ( SQL Express ) it is only a shame that they forgot that even a
administrator of a system should be restricted access from a db from a
programmers point of view in some situations

Hope to have given you some ideas

regards

Michel Posseth [MCP]

"Miro" <mi******@golden.net> schreef in bericht
news:eh**************@TK2MSFTNGP05.phx.gbl...

Ok I have been slowely - and ever so slowely teaching myself VB.net

Currently I have created an MDB file by code, and added fields to the MDB
file by code.
I like this solution because, ( im assuming ) if I create an EXE and I
load an MDB file, I can
see if certain fields are there, and if not add them.
Kinda like an Update that is imbeded into the EXE, so you dont always have
to create an Install shield.

So... Lets say my goal is to have an application that I would like people
to install somewhere.
Why choose SQL Express over a simple MDB file? ( i have never tried SQL
Express )

1. As I am assuming...SQL express is a second install that a user would
have to install ontop of my
application install ?

2. MDB files would be easier to work with because everyone till now has
been working with
MDB files so any help required is easier to get to ?

3. People have told me MDB files will slowely be processed out and SQL
Express will take its place.
Is this true ?

So if you were to write an application from scratch. Would you still go
with SQL Express ?

I am knocking my head back and forth on this. And would like to know how
i will create my db's before i start
trying to code an app.

Thank You,

Miro

[Miro]

I did like the point that was made that the Access mdb can have a password
so only your program can access it.

The SQL Express i am assuming cannot have a password on it so data can be
viewd from everywhere.

Maybe my solution will be to use both.

I will try SQL Express / Light... and see how it goes. Can someone please
confirm / tell me who does use SQL Express
or Light -> Is there a way to secure the DB so only the program can access
/ view the database.

Thanks

Miro
"Dennis" <De****@discussions.microsoft.com> wrote in message
news:A4**********************************@microsof t.com...

If I read your comment correctly, if I have MSDE installed, then I can
install an application that uses SQL Express...is this correct? Also, is
MSDE installed with Windows XP Professional automatically? Thanks for any
info you can provide as I am considering switching to SQL Express.
--
Dennis in Houston
"Michel Posseth [MCP]" wrote:

> 1. As I am assuming...SQL express is a second install that a user
> would
> have to install ontop of my
> application install ?

well a lot of people nowadays have a sql express or MSDE instance
running
without even knowing it

> 2. MDB files would be easier to work with because everyone till now
> has
> been working with
> MDB files so any help required is easier to get to ?

if you know for sure all people have Jet oledb installed ( this is not
standard annymore in MDAC since version 2.6 )
okay having office installed will also work :-)

> 3. People have told me MDB files will slowely be processed out and

SQL

> Express will take its place.
> Is this true ?

In my opinion yes , you could also go for the firebird DB engine wich
has
a verry nice .Net API is completely free ( without anny restrictions ,
and
has even an embedded version ) http://firebird.sourceforge.net/
however
it is not as "friendly" to start with as MSSQL

> So if you were to write an application from scratch. Would you still
> go
> with SQL Express ?

This depends on the project for me .

Why would i choose Access ( i prefer the 2000 db ) above sql express
1. small ( i should say smaller ) footprint
2.deployable to all Windows versions inclusive win 9.x
3. security and then i mean the possibility to secure so no one else
except
you can access the database
while still having the posibility to use indexes etc etc on the data (
this is done with a workgroup information file , using this technique you
can add user roles and encrypt the database )

by the way i believe the best database there is at this moment is MS SQL
2005 ( SQL Express ) it is only a shame that they forgot that even a
administrator of a system should be restricted access from a db from a
programmers point of view in some situations

Hope to have given you some ideas

regards

Michel Posseth [MCP]

"Miro" <mi******@golden.net> schreef in bericht
news:eh**************@TK2MSFTNGP05.phx.gbl...

> Ok I have been slowely - and ever so slowely teaching myself VB.net
>
> Currently I have created an MDB file by code, and added fields to the
> MDB
> file by code.
> I like this solution because, ( im assuming ) if I create an EXE and I
> load an MDB file, I can
> see if certain fields are there, and if not add them.
> Kinda like an Update that is imbeded into the EXE, so you dont always
> have
> to create an Install shield.
>
> So... Lets say my goal is to have an application that I would like
> people
> to install somewhere.
> Why choose SQL Express over a simple MDB file? ( i have never tried
> SQL
> Express )
>
> 1. As I am assuming...SQL express is a second install that a user
> would
> have to install ontop of my
> application install ?
>
> 2. MDB files would be easier to work with because everyone till now
> has
> been working with
> MDB files so any help required is easier to get to ?
>
> 3. People have told me MDB files will slowely be processed out and SQL
> Express will take its place.
> Is this true ?
>
> So if you were to write an application from scratch. Would you still
> go
> with SQL Express ?
>
> I am knocking my head back and forth on this. And would like to know
> how
> i will create my db's before i start
> trying to code an app.
>
> Thank You,
>
> Miro
>
>

[Michel Posseth [MCP]]

Well here we go again
what if the data makes the value for your program ???

in my previuous job i was a catalogue programmer for the Automotive
aftermarket

http://www.nohausystems.com/ ( company i worked for )

you also have

http://www.tecdoc.com

http://www.alldata.com/

http://www.aldoc.nl/main.html

etc etc etc

They all do basicly the same thing , hundreds of people are gathering this
information worldwide for different company`s
they difference by the quality of there gathered data ( it is nice to see
that a ordered part actually fits on the right car )

So you understand that no one should be able to see the internall data
structure etc etc , this is giving the actuall value to the program that
is why thousands of shop`s buy these programs ( believe me this is big
business ) .

So no , i did not make a mistake sometimes you want data to be accessible
only by your program ( all the above company`s protect there data ,,
believe me i tried :-) )
regards

Michel Posseth



"raibeart" <ra******@gmail.com> schreef in bericht
news:11**********************@c74g2000cwc.googlegr oups.com...

I think you have it backwards from the Administrator's point of view.

Programmers should always be restricted.
Michel Posseth [MCP] wrote:

2005 ( SQL Express ) it is only a shame that they forgot that even a
administrator of a system should be restricted access from a db from a
programmers point of view in some situations

[Michel Posseth [MCP]]

Hi Miro ,

All "reall" RDBMS systems have there security based on the local system
rights
i.o.w. an Administrator hass all rights so he can grant rights to the
database so anyone can view the data

With Access i am able to create a database that does not allow the
administrator or anyone else to open, view , or modify the data
i can simply create my own user with my own password ( that does not have to
exist on the system where the program is running )
and can thus open my database through my program with these user credentials

an option in SQL would be to use encryption on the data level , however
this will result in poor performance

regards

Michel Posseth

"Miro" <mi******@golden.net> schreef in bericht
news:eO*************@TK2MSFTNGP02.phx.gbl...

I did like the point that was made that the Access mdb can have a password
so only your program can access it.

The SQL Express i am assuming cannot have a password on it so data can be
viewd from everywhere.

Maybe my solution will be to use both.

I will try SQL Express / Light... and see how it goes. Can someone please
confirm / tell me who does use SQL Express
or Light -> Is there a way to secure the DB so only the program can
access / view the database.

Thanks

Miro
"Dennis" <De****@discussions.microsoft.com> wrote in message
news:A4**********************************@microsof t.com...

If I read your comment correctly, if I have MSDE installed, then I can
install an application that uses SQL Express...is this correct? Also, is
MSDE installed with Windows XP Professional automatically? Thanks for
any
info you can provide as I am considering switching to SQL Express.
--
Dennis in Houston
"Michel Posseth [MCP]" wrote:

> 1. As I am assuming...SQL express is a second install that a user
> would
> have to install ontop of my
> application install ?

well a lot of people nowadays have a sql express or MSDE instance
running
without even knowing it

> 2. MDB files would be easier to work with because everyone till now
> has
> been working with
> MDB files so any help required is easier to get to ?

if you know for sure all people have Jet oledb installed ( this is not
standard annymore in MDAC since version 2.6 )
okay having office installed will also work :-)

> 3. People have told me MDB files will slowely be processed out and
SQL
> Express will take its place.
> Is this true ?

In my opinion yes , you could also go for the firebird DB engine wich
has
a verry nice .Net API is completely free ( without anny restrictions ,
and
has even an embedded version ) http://firebird.sourceforge.net/
however
it is not as "friendly" to start with as MSSQL
> So if you were to write an application from scratch. Would you still
> go
> with SQL Express ?

This depends on the project for me .

Why would i choose Access ( i prefer the 2000 db ) above sql express
1. small ( i should say smaller ) footprint
2.deployable to all Windows versions inclusive win 9.x
3. security and then i mean the possibility to secure so no one else
except
you can access the database
while still having the posibility to use indexes etc etc on the data (
this is done with a workgroup information file , using this technique
you
can add user roles and encrypt the database )

by the way i believe the best database there is at this moment is MS SQL
2005 ( SQL Express ) it is only a shame that they forgot that even a
administrator of a system should be restricted access from a db from a
programmers point of view in some situations

Hope to have given you some ideas

regards

Michel Posseth [MCP]

"Miro" <mi******@golden.net> schreef in bericht
news:eh**************@TK2MSFTNGP05.phx.gbl...
> Ok I have been slowely - and ever so slowely teaching myself VB.net
>
> Currently I have created an MDB file by code, and added fields to the
> MDB
> file by code.
> I like this solution because, ( im assuming ) if I create an EXE and I
> load an MDB file, I can
> see if certain fields are there, and if not add them.
> Kinda like an Update that is imbeded into the EXE, so you dont always
> have
> to create an Install shield.
>
> So... Lets say my goal is to have an application that I would like
> people
> to install somewhere.
> Why choose SQL Express over a simple MDB file? ( i have never tried
> SQL
> Express )
>
> 1. As I am assuming...SQL express is a second install that a user
> would
> have to install ontop of my
> application install ?
>
> 2. MDB files would be easier to work with because everyone till now
> has
> been working with
> MDB files so any help required is easier to get to ?
>
> 3. People have told me MDB files will slowely be processed out and
> SQL
> Express will take its place.
> Is this true ?
>
> So if you were to write an application from scratch. Would you still
> go
> with SQL Express ?
>
> I am knocking my head back and forth on this. And would like to know
> how
> i will create my db's before i start
> trying to code an app.
>
> Thank You,
>
> Miro
>
>

[Michel Posseth [MCP]]

The answer is Yes if you mean if they can run side by side

MSDE installed with Windows XP Professional automatically? Thanks for any
info you can provide as I am considering switching to SQL Express.
Well i do not no that for sure however a lot of the server functionality
uses MSDE in the background ( IIS for instance ) so it wouldn`t suprise me

regards

Michel Posseth [MCP]


"Dennis" <De****@discussions.microsoft.com> schreef in bericht
news:A4**********************************@microsof t.com... If I read your comment correctly, if I have MSDE installed, then I can
install an application that uses SQL Express...is this correct? Also, is
MSDE installed with Windows XP Professional automatically? Thanks for any
info you can provide as I am considering switching to SQL Express.
--
Dennis in Houston
"Michel Posseth [MCP]" wrote:

> 1. As I am assuming...SQL express is a second install that a user
> would
> have to install ontop of my
> application install ?

well a lot of people nowadays have a sql express or MSDE instance
running
without even knowing it

> 2. MDB files would be easier to work with because everyone till now
> has
> been working with
> MDB files so any help required is easier to get to ?

if you know for sure all people have Jet oledb installed ( this is not
standard annymore in MDAC since version 2.6 )
okay having office installed will also work :-)

> 3. People have told me MDB files will slowely be processed out and

SQL

> Express will take its place.
> Is this true ?

In my opinion yes , you could also go for the firebird DB engine wich
has
a verry nice .Net API is completely free ( without anny restrictions ,
and
has even an embedded version ) http://firebird.sourceforge.net/
however
it is not as "friendly" to start with as MSSQL

> So if you were to write an application from scratch. Would you still
> go
> with SQL Express ?

This depends on the project for me .

Why would i choose Access ( i prefer the 2000 db ) above sql express
1. small ( i should say smaller ) footprint
2.deployable to all Windows versions inclusive win 9.x
3. security and then i mean the possibility to secure so no one else
except
you can access the database
while still having the posibility to use indexes etc etc on the data (
this is done with a workgroup information file , using this technique you
can add user roles and encrypt the database )

by the way i believe the best database there is at this moment is MS SQL
2005 ( SQL Express ) it is only a shame that they forgot that even a
administrator of a system should be restricted access from a db from a
programmers point of view in some situations

Hope to have given you some ideas

regards

Michel Posseth [MCP]

"Miro" <mi******@golden.net> schreef in bericht
news:eh**************@TK2MSFTNGP05.phx.gbl...

> Ok I have been slowely - and ever so slowely teaching myself VB.net
>
> Currently I have created an MDB file by code, and added fields to the
> MDB
> file by code.
> I like this solution because, ( im assuming ) if I create an EXE and I
> load an MDB file, I can
> see if certain fields are there, and if not add them.
> Kinda like an Update that is imbeded into the EXE, so you dont always
> have
> to create an Install shield.
>
> So... Lets say my goal is to have an application that I would like
> people
> to install somewhere.
> Why choose SQL Express over a simple MDB file? ( i have never tried
> SQL
> Express )
>
> 1. As I am assuming...SQL express is a second install that a user
> would
> have to install ontop of my
> application install ?
>
> 2. MDB files would be easier to work with because everyone till now
> has
> been working with
> MDB files so any help required is easier to get to ?
>
> 3. People have told me MDB files will slowely be processed out and SQL
> Express will take its place.
> Is this true ?
>
> So if you were to write an application from scratch. Would you still
> go
> with SQL Express ?
>
> I am knocking my head back and forth on this. And would like to know
> how
> i will create my db's before i start
> trying to code an app.
>
> Thank You,
>
> Miro
>
>

[William \(Bill\) Vaughn]

Miro,
This is one of the most hotly debated topics around so expect quite a
few opinions. My TechEd talk (which might be posted online on the Microsoft
site sometime in the near future) discusses where SQL Server Express Edition
fits in relation to JET/Access and the newest DBMS system SQL Server
Everywhere (SQL Ev). Yes, there are a lot of choices and each has its place.
A number of factors should be considered when you're trying to decide which
approach to take.
I won't burden you with the details here, but I did post a new blog
entry to try to highlight the issues. See
http://betav.com/blog/billva/2006/06...ss_j.html#more

hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

"Miro" <mi******@golden.net> wrote in message
news:eh**************@TK2MSFTNGP05.phx.gbl...

Ok I have been slowely - and ever so slowely teaching myself VB.net

Currently I have created an MDB file by code, and added fields to the MDB
file by code.
I like this solution because, ( im assuming ) if I create an EXE and I
load an MDB file, I can
see if certain fields are there, and if not add them.
Kinda like an Update that is imbeded into the EXE, so you dont always have
to create an Install shield.

So... Lets say my goal is to have an application that I would like people
to install somewhere.
Why choose SQL Express over a simple MDB file? ( i have never tried SQL
Express )

1. As I am assuming...SQL express is a second install that a user would
have to install ontop of my
application install ?

2. MDB files would be easier to work with because everyone till now has
been working with
MDB files so any help required is easier to get to ?

3. People have told me MDB files will slowely be processed out and SQL
Express will take its place.
Is this true ?

So if you were to write an application from scratch. Would you still go
with SQL Express ?

I am knocking my head back and forth on this. And would like to know how
i will create my db's before i start
trying to code an app.

Thank You,

Miro

[Miro]

Yes I can see that each has its own +'s and minus's

In my case my final solution was to write it with standard mdb files ( jet )
and then later
make an sql express version.
Im still learning vb, but for me,
1. Not too complicate things for me nor users.
2. Keep it simple. Its not gonna be a master huge great program. Just
something for me to create and learn
vb.net at the same time.
3. Users are not computer savvy, so its easier for 1 install, and me to
handle everything programmatically.
4. Im use to jet files, so learning vb.net with something that is at least
a tad familiar.

Thank you all for all the posts.

If I would have known there was another discussion on the same thing earlier
in this newsgroup I would have posted
and read all those first. Ill search harder next time.

Thank you again,

Miro

"William (Bill) Vaughn" <bi**************@nwlink.com> wrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...

Miro,
This is one of the most hotly debated topics around so expect quite a
few opinions. My TechEd talk (which might be posted online on the
Microsoft site sometime in the near future) discusses where SQL Server
Express Edition fits in relation to JET/Access and the newest DBMS system
SQL Server Everywhere (SQL Ev). Yes, there are a lot of choices and each
has its place. A number of factors should be considered when you're trying
to decide which approach to take.
I won't burden you with the details here, but I did post a new blog
entry to try to highlight the issues. See
http://betav.com/blog/billva/2006/06...ss_j.html#more

hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no
rights.
__________________________________

"Miro" <mi******@golden.net> wrote in message
news:eh**************@TK2MSFTNGP05.phx.gbl...

Ok I have been slowely - and ever so slowely teaching myself VB.net

Currently I have created an MDB file by code, and added fields to the MDB
file by code.
I like this solution because, ( im assuming ) if I create an EXE and I
load an MDB file, I can
see if certain fields are there, and if not add them.
Kinda like an Update that is imbeded into the EXE, so you dont always
have to create an Install shield.

So... Lets say my goal is to have an application that I would like people
to install somewhere.
Why choose SQL Express over a simple MDB file? ( i have never tried SQL
Express )

1. As I am assuming...SQL express is a second install that a user would
have to install ontop of my
application install ?

2. MDB files would be easier to work with because everyone till now has
been working with
MDB files so any help required is easier to get to ?

3. People have told me MDB files will slowely be processed out and SQL
Express will take its place.
Is this true ?

So if you were to write an application from scratch. Would you still go
with SQL Express ?

I am knocking my head back and forth on this. And would like to know how
i will create my db's before i start
trying to code an app.

Thank You,

Miro