i have built a survey database which has one main table Survey, customers
and employees, these tables are related. then because there are so many
fields and drop down boxes i had to create 8 reports related to survey table
. The forms are 8 because of so much detail i have created main form add
customer then the sub forms are all tab subforms . but form i customer is
customer details , then subform 2 has the date and surveyorder number and
employee details, other subforms just have alot of info but have to relate
and have same date employee customer and surveyorder number. I think that
covers it.
Ok... you've made THE most common mistake for survey type data:
adding one field per question. This design is simply WRONG and will
cause you endless trouble. It sounds like (as is also very common) you
designed your table structures to fit the desired report. That's
backwards! You should design your table structures relationally (as
tall-thin tables), and THEN design the Report to print out that data.
Your Survey may benefit from considering Duane Hookum's excellent "At
Your Survey" sample database:
http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='At Your Survey 2000'
This uses one *record* per question, rather than one *field* per
question.
If you're stuck with (or committed to) the incorrectly normalized
table structure, please do as I have requested SEVERAL times: this
time I'll try to be as specific as possible.
Open your Form. View its Properties. On the Data tab the first line is
"Recordsource". Post the value of the Recordsource property.
View the properties of the first Subform. If its Recordsource is a
Query, please open that Query in SQL view. Copy and paste the SQL text
to a message here. Do the same for the third (first of the Survey
data??) Subform. (No need to do all 8 subforms unless they are
dramatically different in structure; two is enough).
Also please post the values of the Master Link Field and Child Link
Field properties of the two Subform controls.
Remember - YOU can see your database. You know its structure and how
its forms are set up. We can't.
John W. Vinson[MVP]