To quote Jack from LOST, "Are you insane?"
While debatable it's really not the central point...
No no no. Not your sanity - the sanity of using Access... That must be very not fun.
Well, that was my second choice on how to take the comment. But I thought the first one was funnier, so I went with it...
...But yes it's been about as much fun as being roasted alive.
It makes me wonder if there is any way to "trick" the system into thinking that it's using Access but actually have a different RDBMS there. Then it would be possible to swap it out.
Sure, it's (a web site) just a bunch of page scripts and an mdb file. The problem is it's a production system and there currently just isn't the time available to risk borking the whole thing if I happen to (miss a db trigger event, etc.) get something wrong.
Sure the SQL syntax is close enough that I could probably just recreate the db and update the connection string to target a MySQL db, and then import the data. But if anything went wrong ... I'd be married to the thing for a string of all nighters trying to stitch the data back together. Sure eventually it will have to be done ... But for here and now, it's (bandaid time) triage only.