ASP + Access

[toString]

What's this like? I've always been a SQL Server guy.
But for a friend's personal website, like everyone has these days - very few hits, would access be any good?

I assume it's easy to connect to one, just a simple change in the connection string. But are they any good to use?

We're talking a random image generator + a news listing/builder. Contact form, etc.

 

[GravyMonster]

access is fine for a small site. a random image generator and things should be fine.

as well as the connection string, access has a fair few differences from SQL in it's queries. the simple stuff is the same - ie. select, update and delete, but dates must be given # delimiters and the join syntax is just plain retarded for example.

 

[HTMLHugo]

im using acces on a few of my small dbs (personal sites etc)

just simple login details etc

never really had any problems but dont push it in any way whatsoever either which you probably wouldnt for hwta your looking for .

What's this like? I've always been a SQL Server guy.
But for a friend's personal website, like everyone has these days - very few hits, would access be any good?

I assume it's easy to connect to one, just a simple change in the connection string. But are they any good to use?

We're talking a random image generator + a news listing/builder. Contact form, etc.

 

[huppy]

I find it okay as long as the site is small - which it is, you say . The problem with Access (or more accurately the Jet driver) is it can only take so many connections at one time before the whole thing keels over and just point blank refuses to work. It is believed the number is about 10 but it depends on what each database connection is doing, and the load put upon the driver and database.

 

[toString]

Thanks that's all good to hear

I assume it's a good idea to .close() the connection at the end of each page?
Must admit I never really bothered with SQL Server.

 

[therubble]

You should always close your connections, never let them fall out of scope.