Object to relational mapping is a quite well improved technique, so, getting benefits of relational database performances (for object persistency, like EJB) is not a bad idea, although I think Access is not the best (compared to Oracle, MySQL...).

I know two products, by ObjeXion (but many others exists; see the OMG site) that will make this for you. Model prototyper reads a Rose class diagram and turns it into an Access database; then Facsimile allows object creation / modification / destruction with a classic GUI or a COM interface.

Netsilon is more web-oriented in that it can generate PHP, Servlet or JSP, using databases MySQL, Oracle or PostgreSQL. You can imagine generate (full java code) only for class diagrams and use generated classes that will be auto-persistent in the database. You can also generate a web interface for object administration. Contact support at objexion.com for more informations.

Usually, a OO Database such as Oracle8 is used. However, if you want to use other databases such as Access, you can use it. You may generate DDL (SQL script) for the classes and create the tables during implementation. Remember that you are not taking the advantage of OO completely in this case.

UML is not a methodology, it's a modelling language. And it can model databases and even processes, so the answer is no. You may wish to model an adapter class between your database and your OO stuff. Have a look at www.rational.com to see one UML based development methodology.

Dermot