Brian Hogan wrote in post #960756: > Adapters are actual ActiveRecord adapters. There's no msaccess adapter > available, although there is a SqlServer adapter. > > If you can get the connection going through ODBC, you could probably > write > your own msaccess adapter - they're not that hard to write and you could > use > the sqlite3 adapter as a template.
Why not just use the ODBC adapter? > > I've never successfully gotten a Rails app to talk to MS Access and I've > been at this a long long time. My recommendation is to convert the > access db > to mysql or sqlserver and go from there. I'd actually recommend neither of those, but would suggest PostgreSQL instead. > (We used to do ASP pages with > MS > Access - let me just say that web apps + ms access == recipe for > disaster.) Really? To be sure, Access is a pretty bad DB, but I remember doing production Web applications with ColdFusion and ODBC/Access way back in 1999, when no one knew any better. I don't recall major DB issues, though it's possible that the sysadmin didn't mention them. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
