soooo basically if I use asp like this site for example only 8 people can assess a certian part of my site at a time? so I and 7 other people click on the default page from some other site and if a ninth person is also doing it then CRASH!!! so why are they so interested in teaching it (especilly asp .NET) at school? Because it is Micro$oft? Well I do not expect allot of people on my site so I will probably go with asp. I guess I will use cfm for another... and php for the anime site. that one I expect allot of people over time. The site I am thinking about is windows. I guess the anime site will be linux.

register_globals.... cout>answer;

cout<<

Joe, what paxx was referring to is that Microsoft Access is not an industrial strength database. It's not meant to be. It's meant to be a desktop database that can handle relatively few simultaneous connections. So its good for test/learning purposes or really small non-desktop applications. (I don't know what kind of load Access can handle).

In the real world, .NET applications use Microsoft's more industrial strength database called MS SQL Server.

Or they could use IBM's DB2 or Oracle, as long as there is an ODBC driver or ADO driver to allow third party databases to interact with the .NET platform.

Or you could use MySQL since it probably has an ODBC driver.

I don't know about using CFM (Cold Fusion) as Crae says, it costs money. And I don't know if you have access to IIS and ASP (depends on what OS you have).

A totally free alternative is to use Apache web server with PHP as your processing backend and MySQL or ProgreSQL as your database server.

Not sure if MySQL has an ODBC thing. The only experience I have with it is in combination with Apache and PHP. MySQL then has its own daemon listening on port something something, so you have the sql server running next to the httpd server (Apache in my case). PHP then accesses it via localhost and the correct port.

By the way, what I heard about Access is that it can only handle one connection at the same time. So weird!

Crae, I thought I saw an ODBC driver for MySql somewhere, but I could be wrong (this was a long time ago). As for Access, one of my previous jobs, the company wanted to switch over to Access for the backend of ther enterprise app in order to offer a cheaper alternative. It was comedic, it sort of worked but was terrible and ended up giving up on the idea (at least while I was still there).

No craeonics, MS Access can handle 8 simultaneous connections.

joetheblow: From what I understand, it doesn't mean that no more than 8 people can visit your site at the same time, it basically means that no more than 8 people can call the database at the same time. In other words, if every page of your site retieved data from an Access database, no more than 8 people could click on a link at the same time. Once the page has been retrieved and the visitor is reading it, it doesn't count as a connection anymore until he clicks on a link again. And no, the 9th person wouldn't crash but would receive a message of this sort "The maximum number of connections has been reached. Please try again later." Or something like that.

oooooooooohhhhhhhhh.......

thanks for the insite...

apache and php sounds really good.

now I seem to understand access better as far as me using it as a back end for my web site. I will come up with a better statagy depending on what I use.

It will be a few months before anything gets really started. I wil be sure to ask more questions later.