The closest (IMO) thing to Access that works with MySQL is OpenOffice's DBA stuff. Personally, I prefer to set up and maintain the DB structure by hand (tends to take less time once you're used to it) through simple text files, use OO to make a cute little Access-like frontend (if you don't want a web-based frontend, or custom coded interface), which has the added benefit that once you get MySQL and OpenOffice interoperating (simple, but perhaps confusing to a Linux/MySQL/OO newbie), then you're set up to use the DB in writer, calc, impress, etc.
If you're proficient with Access, then OO's form creater will feel just about right. (Once you get used to the various quirks you have whenever you change software.) If you're not a big fan of Access (I'll spare you my rant) OO's interface will drive you just as batty.
For the record, I used to wonder why Linux didn't have any good Access-like interfaces. Play with databases enough, and you'll realize how inefficient they are. You spend more time moving around hitting the correct icon/buttons than you do actually thinking about how things are being set up. Plus, there's a layer of abstraction that MS loves to insert, that keeps you from really understanding how a DB works. For rapid prototyping, or testing out an idea, it's quick and dirty. For actual implementation and maintenance, it's a headache waiting to happen, IMHO.
Not that it's bad, but if you plan on doing this for work, it would behoove you to examine alternate approaches to DB creation. Nothing like the simplicity of typing:
mysql -u myname -p < textfilewithsql
Hmmm, guess I ranted anyway. Sorry.