The SQL should work without changes,
as SQL is pretty DB independant for simply statments
To actually convert the data and get it into the MySQL database, there are several converters, including:
[cynergi.net ] (free, but you have to compile it yourself in visual basic)
[mdb2mysql.de ]
[webattack.com ] (shareware, $39.95)
and finally
[dbtools.com.br ], which is insofar as i'm aware: free, easy & small. just click downloads and follow the instructions & links.
HTH,
William
Good luck,
Dw
heres a couple of links in case you don't have them already:
theres a link at the top to join, its a pretty good list but quite high traffic.
[servlets.com...]
a good book on servlets
[oreilly.com...]
a good book on jsp
[java.sun.com...]
the jsp spec.
I havn't used EJB yet, as far as I can see unless you have a big site that needs load balancing its a bit overkill, interesting stuff tho ;)
oops, forgot: popular open source jdbc driver for mysql:
The lack of row level locking means that you can't have 2 people editing a table at the same time - IE: placing an order at the exact same time which would require a write to the db. The chances of this occurring increase with the number of transactions being executed. Without row level locking, 1 user will have to wait while the other's transaction is processed and recorded. Not a big deal on smaller web sites but can be a major headache if you do a lot of sales with your web site. How you handle this as a programmer is up to you. Some folks let the user wait while others notify them the db is busy. Don't let this minor issue keep you from using MySQL. It is a very quick and reliable database not to mention its free and well supported.
What would happen if 3 people logged in at the same time and tried to hit the save button?
Would there be an error message, or would one just wait?
I recently did a demo with 40 people on the same account with Access and there wasn't a problem at all.
This concerns me now.
Will MySQL keep trying until it's successful or times out - I'm not sure.
MySQL will return an error code and an error number if it can't complete the query which you can capture and use: for the error in a readable text format use mysql_error() and for the code use mysql_errno(). I don't know if will return an error for the table being busy (it must!) nor what the code number is but if/when you find it you could use it in your code to tell the user to wait or to try the submission again in 50 milliseconds. HTH
what you need for transactions is mysql-max, which is an extended version which supports transactions through use of the innoDB tables (http://www.innodb.com/ -erm- its alright to post URLs like this right?). The good news is you can get a binary of the whole lot together at the mysql site. Theres documentation on it there too, also more documentation at the innoDB site.
you can use transactions in your beans through JDBC, which you use to connect to the db. As far as I'm aware the mm.mysql driver supports transactions.