[AccessD] Presenting data problem

Arthur and Jim;

I'm seriously considering this route. The db is small enough that even if
in the future it proves troublesome, it should be easy to fix or even
rework.

Tomorrow, I will see about building a second table that defines the
disposition record -- and including all the possibilities in that one
table. I don't mind the blanks and Arthur's absolutely right, with the
right query, I can present the right fields using the same query/input form
with only one data source -- which is genius as far as I'm concerned.
Certainly will simplify things on my end.

Thank you!
Susan H.

On Tue, Oct 28, 2014 at 5:16 PM, Jim Dettman <jimdettman at verizon.net> wrote:

> Susan,
>
>  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.
>
>