23 page report, completely blank

[Mandu]

The layout header is light gray with some black text. The rest of the layout is a subsummary line. A footer contains the text "hi there".

Viewed in Preview mode there are 23 pages, completely and utterly white.

Everything is set to be printable.

It was working until I did some fiddling, so most likely it was one thing I did to make everything invisible.

Does this make anyone go "ah-hah"?

Gratefully,

Chap

[Mandu]

The layout header is light gray with some black text. The rest of the layout is a subsummary line. A footer contains the text "hi there".

Viewed in Preview mode there are 23 pages, completely and utterly white.

Everything is set to be printable.

It was working until I did some fiddling, so most likely it was one thing I did to make everything invisible.

Does this make anyone go "ah-hah"?

Gratefully,

Chap

[Mandu]

The layout header is light gray with some black text. The rest of the layout is a subsummary line. A footer contains the text "hi there".

Viewed in Preview mode there are 23 pages, completely and utterly white.

Everything is set to be printable.

It was working until I did some fiddling, so most likely it was one thing I did to make everything invisible.

Does this make anyone go "ah-hah"?

Gratefully,

Chap

[dkemme]

Make sure you have some records in the found set at the time of printing.

[dkemme]

Make sure you have some records in the found set at the time of printing.

[dkemme]

Make sure you have some records in the found set at the time of printing.

[Himitsu]

well, the biggest ah hah I get is if your subsummary is sorted by a field, and you don't have that SAME field in that part, you will get a lot of nothing... and... when you create the report and have FMP create a script, it sets the sort for the order you put the report together. So, the first subsummary should have a sort that is somewhat related to it. If your first subsummary is by date, then the script sort shouldn't be by size of french fries.... then of course if you have a body part you should make sure that it has something to do with being below in data from the subsummary. Many problems come when someone doesn't think of the hiarchy of data... what is common, less common, and least common. You shouldn't put least common data first then put commmon data in the body.... I don't know if that helps but check the subs... then move to the script...

If you changed the fields because you would rather see another kind of data,then you have to make sure the subsummary part is summarizing that field and not the old field you had in it.

[Himitsu]

well, the biggest ah hah I get is if your subsummary is sorted by a field, and you don't have that SAME field in that part, you will get a lot of nothing... and... when you create the report and have FMP create a script, it sets the sort for the order you put the report together. So, the first subsummary should have a sort that is somewhat related to it. If your first subsummary is by date, then the script sort shouldn't be by size of french fries.... then of course if you have a body part you should make sure that it has something to do with being below in data from the subsummary. Many problems come when someone doesn't think of the hiarchy of data... what is common, less common, and least common. You shouldn't put least common data first then put commmon data in the body.... I don't know if that helps but check the subs... then move to the script...

If you changed the fields because you would rather see another kind of data,then you have to make sure the subsummary part is summarizing that field and not the old field you had in it.

[Himitsu]

well, the biggest ah hah I get is if your subsummary is sorted by a field, and you don't have that SAME field in that part, you will get a lot of nothing... and... when you create the report and have FMP create a script, it sets the sort for the order you put the report together. So, the first subsummary should have a sort that is somewhat related to it. If your first subsummary is by date, then the script sort shouldn't be by size of french fries.... then of course if you have a body part you should make sure that it has something to do with being below in data from the subsummary. Many problems come when someone doesn't think of the hiarchy of data... what is common, less common, and least common. You shouldn't put least common data first then put commmon data in the body.... I don't know if that helps but check the subs... then move to the script...

If you changed the fields because you would rather see another kind of data,then you have to make sure the subsummary part is summarizing that field and not the old field you had in it.

[Mandu]

Thanks for the suggestions. The found set was populated and properly sorted, and the layout *seemed* to be correct in terms of its subsummary break field (it had worked originally but seems to have broken during some cosmetic touch-ups).

Finally I just created a new, "identical" layout and it worked again. Not worth chasing the problem!

[Mandu]

Thanks for the suggestions. The found set was populated and properly sorted, and the layout *seemed* to be correct in terms of its subsummary break field (it had worked originally but seems to have broken during some cosmetic touch-ups).

Finally I just created a new, "identical" layout and it worked again. Not worth chasing the problem!

[Mandu]

Thanks for the suggestions. The found set was populated and properly sorted, and the layout *seemed* to be correct in terms of its subsummary break field (it had worked originally but seems to have broken during some cosmetic touch-ups).

Finally I just created a new, "identical" layout and it worked again. Not worth chasing the problem!