Tough group header problem :(

[Guest]

I have a report group header that gets cut off, prints partially, or doesn't
print at all if it appears near the bottom of the page. If I change the
"Keep Together" property to "No" then it will
print part of the group header but the next page won't have the rest of the
group header data. Even if there's not enough room for the
group header, Access will try to fit it any it won't even print the rest of
the
data on the next page. I tried all combinations of the sorting and grouping
keep together as well as the group header keep together property. How do you
solve this problem?
Thanks for any help
-rf

 

[Marshall Barton]

I have a report group header that gets cut off, prints partially, or doesn't
print at all if it appears near the bottom of the page. If I change the
"Keep Together" property to "No" then it will
print part of the group header but the next page won't have the rest of the
group header data. Even if there's not enough room for the
group header, Access will try to fit it any it won't even print the rest of
the
data on the next page. I tried all combinations of the sorting and grouping
keep together as well as the group header keep together property. How do you
solve this problem?

Sounds strange.

What happens if the header starts near the top of the page?
Maybe you have something in the header section that's
confusing Access???

The only thought I have is to make sure the text boxes and
the header section all have their CanGrow property set to
Yes.

 

[Guest]

If the header starts at the top of the page it will print. What are some of
things in the header that would confuse Access? I tried all the can grow
properties but it didn't work either...still racking my brains lol
thanks for any help

 

[Marshall Barton]

The things can confuse Access are odd combinations of event
procedure code. I guess I'll need to see all the code
behind the report before I can tell if it might be an issue.

The only other straw grasping thought I have is that there
might be some kind of corruption causing the strange
behavior. If you want to pursue this thought, check:
http://www.granite.ab.ca/access/corruptmdbs.htm