I'm not sure I follow what you're asking. Can you provide an example?

>Thank you for the answer Craig. I think I have not expressed myself clearly. I don't want to overstate the frequency with which attributes will need to be stored as records in Object-Atribute-Value tables (or is it Entity-Attribute-Value) rather than as columns in the application we are developing.
>
>Most of the attributes of our BOs will be known at development time, but we have found that an infinity of new types of time and income categories (that follow different business and tax rules) appear as time goes by and we don't want to create new columns in several tables every time this happens. Rather, we would like to store time and income values as records in a detail table rather than columns in a transaction table, yet have them show up as attributes on a transaction BO. That is what I mean by storing some attribute values as records rather than columns in a table.
>
>We would like this to be handled by the framework we choose. I anticipate there would be an attribute definition table with defaults that is referred to when adding properties to BO.
>
>What do you think?