[AccessD] Presenting data problem

Arthur and Jim;



>  What Arthur has suggested is a middle of the road approach to what is
> called a Entity Attribute Value (EAV) design.   But rather than a single
> table of fields that define things, typically the attributes appear as
> individual records in a single table.  That allows something to have any
> number of attributes.
>
>  It's a great way to handle stuff sometimes.  A classic case is an Asset
> Tracking system where you need to identify different type of things.
>
>