The problem is that I'm somewhat short of ideas on how to make this work.
What kind of data are you collecting and how do you plan to use it?

I'm planning to make FreqID a foreign key on my Incidents table which contains the choices (Yes/No) fields.
You do not need a frequency field (Nor for that matter a tblFrequency) as
your queries can count for you when you need that information.


--
Build a little, test a little.


"omoluabi" wrote:

Hi all,
I'm designing a database that requires users to specify the number of times
a Yes/No field occurs. This number is not required if the choice is No but if
Yes, I plan to create a drop down menu for the user to specify the number of
times the choice occured.
My first thought is to create a Frequency field for each choice but then I
thought there must be a better way to do it. I came up with an idea to create
a Frequency table (tblFrequency) described below:

tblFrequency:
Field: FreqID
Field: Freq

I'm planning to make FreqID a foreign key on my Incidents table which
contains the choices (Yes/No) fields.

The problem is that I'm somewhat short of ideas on how to make this work.
Thanks for your patience.