Am I doing this right? Scaling up database to cope with 35+ users

Hi,



I was hoping someone knowledgeable could advise whether my solution below is the right one.



The short version: does using a MySQL back-end (hosted on internet) and Access front end overcome issues of 30+ users accessing/editing the database at same time?



The longer version...First some background:



I have just finished developing an Access database application that tracks student results for the local school.



I split my front-end from the database back-end.



The plan is to distribute copies of the front end to 35+ teachers, and save the back-end on a network drive.



Now I'm a bit worried that a large number of teachers might try updating the database at the same time with unpredictable results. At first, I thought the database would cope with 15 or so simultaneous users, but I'm guessing anything more could result in errors/problems for the teachers.



My proposed solution.



I tested a MySQL back-end database that was hosted on my internet site (I use a hosting provider with a cPanel setup that gives you MySQL). I'm using Access as the front end and connecting using a MySQL ODBC driver. My first test seemed to run very well (MySQL hosted on the internet was a bit slower of course).



I'm just wondering if this a good solution to my problem (i.e. multiuser access).



Grateful for anyone's advice or pointers to a better solution?



Regards

Des

Am I doing this right? Scaling up database to cope with 35+ users