MSDE or Jet for my application?

[elizabeth baker]

We are developing a fairly simple database to be deployed on the
internet. It consists of an artist's works (approx 2600 of them) based
on references to books from which his ideas came. Relative fields will
be fairly few, data related to the books, a pic of his initial sketch,
and a pic of the final painting. Searches will be provided and probably
a feedback form. The plan is for this database to be used by students
when studying myths of the world (and other interested parties, of course).

i am in the beginning stages using Access 2002 and Jet. We just
purchased and installed Visual Studio .net (academic version), but i
haven't actually used it yet. The install mentions MSDE. However, even
after reading about MSDE on MS's site, i still can't determine my course.

For our web application, what should i use? MSDE or Jet? ADO or is DAO
(i am familiar with DAO but not ADO)?

i need a plan, a course of action to follow for this, as it is new
ground for me. i'm not asking for details, just general direction. i'm
basically self-taught and there is no one here who knows any more about
this.

Any guidance is appreciated.

--e

 

[William Ryan eMVP]

As far as which to use, go with MSDE. Access is nothing but headaches and
isn't a real client server DB. MSDE gives you all the perks of real SQL
Server with the main difference being the 2gb limit, which is the same as
access. YOu'll have much better security, performance, backup/recovery
functionality etc.

As far as accessing the data, if you are using VS.NET, highly recommend
ADO.NET.

 

[Elizabeth Baker]

Thanks, William. i ordered SQL Server 2000 Developer Edition.

How will this affect things? How does everything interrelate?

i'm used to DAO, so i have to learn ADO and about putting the db on the
web. i'd really like to get started out on the right path.

Thanks for your help and any advice you'd like to give.
--e

 

[John Bailo]

As far as which to use, go with MSDE. Access is nothing but headaches and
isn't a real client server DB. MSDE gives you all the perks of real SQL
Server with the main difference being the 2gb limit, which is the same as
access. YOu'll have much better security, performance, backup/recovery
functionality etc.

I second that. From experience with an Access based site using classic Asp,
you can expect to be rebooting your server once a week using Access.

I don't think the ODBC drivers are good enough for the multiple connections
and threads that a typical website will open up on a database.

As far as connectivity, if you use SQL Server, you should use the SQLClient
libraries in .NET. They are optimized for SQL Server.

 

[William Ryan eMVP]

Thanks, William. i ordered SQL Server 2000 Developer Edition.

Good choice.

How will this affect things? How does everything interrelate?

You can use the Client Tools (Query Analyzer and Enterprise manager to name
two) to connect to any sql server (which includes MSDE) on your network or
that you can see.

i'm used to DAO, so i have to learn ADO and about putting the db on the
web. i'd really like to get started out on the right path.

ADO.NET is soooo much cooler than either of those. There's a really active
ADO.NET NG and ADO.NET supports a direct Sql library SqlClient
the NG is microsoft.public.dotnet.framework.adonet