Ruby on Rails and MS Access

Although I agree wholeheartedly with all arguments against using MSAccess as a database, some legacy systems do so, and require either exporting or interfacing with.

I haven't upgraded to Rails 2.0 yet, which puts ActiveRecord adapters in gems, but I have an msaccess_adapter written that's done me fine for about a year now.

Microsoft Access adapter:

It most likely won't work with the newest version of ActiveRecord, but it works fine with previous versions (before adapters were moved to gems).

Again, by all means DON'T use Access for your website database. Even sqlite would be better. If you must tie in with an Access database, don't be afraid to use that for the data it has and must remain in the access db, while keeping a mysql or sqlite db beside it for the regular website operations. Among other things are huge speed and stability differences.