normalizing one to one relations with multiple types

[C Hayes]

Here's my scenario:

The scheme is donors who make contributions. Here’s where I have a little
trouble:

The donations are of different types and need to be tracked with different
criteria. For example:

All donations contain generic donation information, i.e. Deposit Date, From
(related), Amount, Batch Number, Event, Type, Check Number etcetera.

A person may make a donation in memory of someone. This type of donation
requires information in regards to a memorial, i.e. the person in memory of,
the family to be notified of the donation etcetera.

Another person may be paying for an item we sell (a cut rate program we
provide as an agreement with a medical company.) I need to track the name of
the person, order numbers, Clinic of origin, etcetera.

Then there are events, with different criteria, etcetera. It grows like
this. Every scenario increases the multiple one to one relationship types to
each donation.

Is there a way to have a table that can switch types? An intermediate table
that has switching types. (Boy, now that sounds complex!)

Thanks in advance for all suggestions.

CS

 

[C Hayes]

then I guess there is the form approach. How would one approach this from a
data entry point of view. Does a type combo box switch controls names
etcetea. Nothing critical here, it's all being handled elsewise but it would
be great. Ideas you dream about outside of work. lol