database structure/design problems. please help

[reservedbcreater]

there are 7 reserves.
each reserve has 200 surevys.
each survey is 17 pages long.

i created a table for each page of the survey(also represents a section of
the survey)

a created a form for each table.

to fill out a survey you fill out a form click next and it takes u to the
next form of the survey until its complete.

i set ID so that there is 1 ID# per each survey. (each table/form has ID#
field)

and i coded it so that each current form closes when u click next to take
u to the next page/form of the survey. also i coded it so that ID# value
is taken from current form and passed to the next form.

it seems to work fine to enter the surveys in to save them to the
DB(tables).

and it is fairly easy to change/add fields too.

Will there be any problems because of my design when i do the database
search/query form????

or are there any design inital design problems b4 i even think about my
search form???????

thanks

 

[Larry Linson]

Without more information, we couldn't give you useful assistance on the
table design. A separate table, related one-to-one with the other tables,
might be an appropriate design, but "one table per page" in many instances
would be a warning that the database may not be properly "normalized" (that
means, done in accordance with relational database design principles). Could
you clarify?

Larry Linson
Microsoft Access MVP

 

[reservedbcreater]

each page of the survey is a different section.
first page is general information.
next page Water
next page Garbage and Sewer
next Exterior
etc.
thats why each page is a table/form