From: Michael Furmaniuk Date: 2009-04-09T02:40:03+09:00 Subject: Re: Mysql::Error Table doesn't exist So, I ended up taking another look at this today and realized I hadn't been paying as much attention to the naming as I would in Rails. Changing: > class TestResults < ActiveRecord::Base to class AutoHarnesses < ActiveRecord::Base and > agents = TestResults.first() to agents = AutoHarnesses.first() I get my query to complete, I didn't realize ActiveRecord here was also using the same naming standards as it does within Rails, but I should have expected that since the access methods seem to be the same. -- Posted via http://www.ruby-forum.com/.