Database Structure

[Jada W.]

I am about to create a new database and I want to make
sure I create it properly at the outset so what I want to
happen can actually happen. Here's what I'm planning:

1. Form (DEMOGRAPHICS) that will contain demographic
information on each client such as name, address, gender,
race.

2. Six evaluation forms that each client can complete

3. Like to have a button on the DEMOGRAPHICS form for
each evaluation form that will open a blank evaluation
form

4. When accessed via the button on the DEMO form, I
would like the corresponding blank eval form to populate
with some of the demographic info. (name, client #) from
the client form that accessed it

5. HOWEVER (and I think this is a big "however"), I
would also like the ability to view completed evaluation
forms when a particular evaluation form is accessed
directly (that is, NOT via the button on the DEMO form)

I hope this is clear. Do I need to create a query
between the DEMO form and each eval form (so there would
be six in all), or some other query combination, or is
this accomplished via the table relationships that I
would create at the beginning of the database process.

Thanks in advance for your help.

- Jada

 

[Pavel Romashkin]

I think that you should start by summarizing the information you are
planning to store in the database. The way you described the forms helps
with this a little bit but is not sufficient to completely construct the
data structure. It is the data (table) structure and relationships that
is critical to successful implementation of your form layouts and, in
the end, database functionality.
What you described is a user interface, a relatively secondary part of
the database that will logically follow from the proper table setup.
It would be helpful to know what are the evaluations that you are
planning to offer. Once you state that, we will be able to recommend
table structures and queries that you can base the forms on.
Good luck,
Pavel