MODELING ADVISE

Hello all,

I have a fairly complex model I am trying to figure out. This is just one
part of it. I have a survey being conducted at a site. Depending on the
site type, a series of information needs to be collected. For example, if
the site is residential, then fields A,B, AND C need to be collected. If
however, the site is a commercial location, then fields A,D,E,F,G etc. need
to be collected.

Question:
should I be putting all the fields, regardless of their type in one table?
--
Carlee

Carlee

I may be fixating on, and over-reacting to, your use of the word "survey",
so take this with a grain of salt...

A fellow MVP has created a very useful application/model of surveys --
please see:

Duane Hookom has a sample survey database at
http://rogersaccesslibrary.com/Other...p#Hookom,Duane

--
Good luck

Jeff Boyce
Access MVP

"Carlee" wrote in message
...
Hello all,

I have a fairly complex model I am trying to figure out. This is just one
part of it. I have a survey being conducted at a site. Depending on the
site type, a series of information needs to be collected. For example, if
the site is residential, then fields A,B, AND C need to be collected. If
however, the site is a commercial location, then fields A,D,E,F,G etc.
need
to be collected.

Question:
should I be putting all the fields, regardless of their type in one table?
--
Carlee

Jeff,
thanks for the reply. My database isn't a "survey" in the typical sense, it
is a method of collecting data for laboratory testing. The use of the term
'survey' is symatical in this situation.

Having said that, can you advise at all on my initial question?

Many thanks in advance



"Jeff Boyce" wrote:

Carlee

I may be fixating on, and over-reacting to, your use of the word "survey",
so take this with a grain of salt...

A fellow MVP has created a very useful application/model of surveys --
please see:

Duane Hookom has a sample survey database at
http://rogersaccesslibrary.com/Other...p#Hookom,Duane

--
Good luck

Jeff Boyce
Access MVP

"Carlee" wrote in message
...
Hello all,

I have a fairly complex model I am trying to figure out. This is just one
part of it. I have a survey being conducted at a site. Depending on the
site type, a series of information needs to be collected. For example, if
the site is residential, then fields A,B, AND C need to be collected. If
however, the site is a commercial location, then fields A,D,E,F,G etc.
need
to be collected.

Question:
should I be putting all the fields, regardless of their type in one table?
--
Carlee

The link suggested by Jeff can be "re-purposed" for modeling more than just
a survey. You could possibly add a table to At Your Survey that identifies
which series of information needs to be applied.

Did you review the demo?

--
Duane Hookom
MS Access MVP
--

"Carlee" wrote in message
...
Jeff,
thanks for the reply. My database isn't a "survey" in the typical sense,
it
is a method of collecting data for laboratory testing. The use of the
term
'survey' is symatical in this situation.

Having said that, can you advise at all on my initial question?

Many thanks in advance



"Jeff Boyce" wrote:

Carlee

I may be fixating on, and over-reacting to, your use of the word
"survey",
so take this with a grain of salt...

A fellow MVP has created a very useful application/model of surveys --
please see:

Duane Hookom has a sample survey database at
http://rogersaccesslibrary.com/Other...p#Hookom,Duane

--
Good luck

Jeff Boyce
Access MVP

"Carlee" wrote in message
...
Hello all,

I have a fairly complex model I am trying to figure out. This is just
one
part of it. I have a survey being conducted at a site. Depending on
the
site type, a series of information needs to be collected. For example,
if
the site is residential, then fields A,B, AND C need to be collected.
If
however, the site is a commercial location, then fields A,D,E,F,G etc.
need
to be collected.

Question:
should I be putting all the fields, regardless of their type in one
table?
--
Carlee