Access v Mysql

[ian_ok]

Hi all.

It's been a while since I was on here. Hi to Rich, Pat and the other regulars.

I'll be running a website that needs a d/b and need some feedback.

What are the main pros and cons with access

What are the main pros and cons with Mysql

I know access and think I could get what I want a lot quicker.

My hosting company charges for using Mysql - I need to keep cost down.

Does access have problems if many people are using the d/b at the same time?

Thanks for any feedback.

Ian

 

[TexRanger]

Hi,
Answer to all your who,what why and whens
1]What are the main pros and cons with access
- Quick Turnaround
- Very Zippi response, provided you configure mysql properly
- Extremely good presentation
- Good master detail design type and versatile forms

2]What are the main pros and cons with Mysql
- same as above, but a wrong config could kill all the pros
- Access+MySQL combination is pretty quirky to get started with.

3]Does access have problems if many people are using the d/b at the same time?
- none that, i encoutered, I have about 50 persons working on a network database (MSQL 2008)

i hope this answers your questions

 

[Pat Hartman]

Comparing Access to MySQL is like comparing apples to oranges. They are both software packages but they don't do the same thing. Access is a RAD tool used to develop applications. It is used to develop the user interface. MySQL is a database management application. It is used to store and manage data. You can compare MySQL to Jet or ACE. Those are the database engines that are closely integrated with Access and and many people mistakenly call them "Access" but they are NOT Access and they can exist without Access and be used by any ODBC compliant software.

Jet/ACE are file servers. They are not database servers and although you can get by using them as the data store for a web page. It only works for very low volume data and concurrent user counts. So the answer is - how many concurrent users to you expect? How much data do you need to store?