Ruby on Rails and MS Access

Rails
21

caused by adapter: access in your database.yml, while no access
adapter available.
Simplest fix I can imagine is to use sqlite adapter along with sqlite
gem installed.

22

PAZAZ wrote:

Thanks for all the replies. The reason I am mentioning Access is b/c I
work in a medical department where we use only Access b/c we really
don’t need the large data capabilities of MySQL and the databases were
created many years back in Access 2000, which serves our needs fine.

But since I am new to ROR and am interested in building my own
applications, I will look into MySQL.

For the question #2 below (which I am pasting below this line)…

  1. I also have a non-Access question that I am putting here so I
    don’t
    have to start another thread. I put in the followoing code (“Ruby
    script/generate model book”)
    into the command line to create a model called book…but I get a
    RunTime Error. How do I fix this?

…this is from a tutorial I am doing to learn ROR and the tutorial
says to create the model book with the one line code above…but when
I put this into the command interface I get a long RunTime Error.

I am a pharmacist and I have a similar isue. All the data is currently
iin MS Access and I have all the data on a remote server. It is often
difficult to get your IS department to go along with new tech, so you
will proibably need to set up a seperate system in parallel with yoru
current infrastructure. As there also HIPPA concerns with patient info
going over netowrks, so I am working on the following strategy:

1.Taking all tables and queries and porting them to MySQL
2.Building the app using these tables
3.Installing the app on a local clinical function workstation that can
access the app as well as the host system using the browser to manage
workflow
4.Mirroring the database on a seperate server & doing migrations every
so often for maintenance

Between HIPAA and IS policies that hinder rather than help solve
problems, this is the safest way to do it. It should allow you to avoid
bumping heads with both your IS and Risk Management departments.

Good luck…

mfb