Reason to Use MySQL over MSAccess2000

[Anon]

I am just getting into php/apache/db development and I am working on a small project of a web based db interface for submitting data and querying (thanks to information from phpbuilder.com and people on forums). To get my boss on board, I had to start with Access2000, b/c that is what he knows and can work with. My IT buddy tells me I should just go straight to MySQL. Besides the info on MySQL.com page, could people send me some legitimate reasons for going the MySQL route over Access2000. Very much appreciate the help.

Thanks
Mike

[[deleted]]

Forget MySQL, go straight to PostgreSQL

Access was never meant to be used as a backend for 'professional' applications. in the first place.

MySQL was designed to be used for professional applications, but it lacks a few 'must-have' features that make it useless for complex apps.

PostgreSQL has all the features you need and can cope with the largest volumes of data that you can imagine. It also has a few crash-recovery and data-integrety features that make it allmost perfect for web-apps.

[gio2k]

MSAccess is a personal database. So forget about it. Access is not an option, at least if you need decent performance.

You have to choose a Database Management System that can cope with your requirements.

If you are going to have many users trying to access your database simultaneously, and you need transactions, then go for PostgreSQL.
Go for PostgreSQL also if you're used to writing complex queries (with subqueries).
If you need Stored procedures and triggers, use a commercial DBMS.

If you don't have too many simultaneous connection and you don't need complex transaction management, you can choose MySQL, because it's faster than PostgreSQL.

-Gio-