rmmcgr wrote:
> Hi,
> 

[snip]

> 
> Some tables have multiple columns where they all reference the code
> table, but for differing code types.  My experience with this has been
> to have one table (the code table) to store many options like this,
> rather than to have lots of little tables that are for situations such
> as storing a list of available options.
> 
> So I guess my question is two fold.  Is this a good practise in the
> first place?  And secondly how would I go about getting rails, and
> ActiveRecord, to work with a code table?
>

This sounds to me like an unwise db schema design, but it's hard to tell 
without at least a small specific example of what you're doing.

> Thanks for any advice/help,
> Regards,
> Richard
> 
> 

-- 
Daryl

"We want great men who, when fortune frowns, will not be discouraged."
     -- Colonel Henry Knox, 1776