What I saw was not the corresponding footer, but a footer of an inner group that started on the new page. It probably also happens when the corresponding footer is the first line, but I did not have a case (I guess I could play with the test records to simulate that), so yes, it looks like it is an old bug that was never fixed.
If MS thinks that it is not necessary to reprint the header when a/the footer starts on a new page I disagree with that, but I think it's more likely this bug was either too small or too complex to make the list. We had R. Stanton presenting his new VFP 9 report engine here in Vancouver, but it was one year ago, so I missed the chance to try to help this bug to jump the queue ;)

>Doru,
>
>Your last response reminded me of something. Many many years ago I mentioned a bug in a FoxTalk article that I wrote (which I can't find right now), and it had to do with Group Headers not reprinting on a new page. Specifically, if I remember correctly, the bug I found had to do with the Group Header NOT reprinting if its corresponding Group Footer was the first thing to print on a new page. If an actual detail band object was the first thing to print on a new page, then the Group Header came out correctly, but not if a Group Footer was the first thing to print.
>
>Is this what you're experiencing? Maybe this phenomenon has never been fixed in any version of FoxPro... I don't know... I haven't tested it. I think I first discovered this back in the old FoxPro/DOS days. Or maybe this behavior is by design... maybe MSFT thinks that a Group Header re-print is not necessary if a Group Footer is going to print at the top of a page. Personally, I consider it a bug.
>
>--Brad