Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

How to Page Break correctly in Report Writer?

618 views
Skip to first unread message

DynamicsGonePartying

unread,
Oct 1, 2008, 7:37:01 PM10/1/08
to
I have a customer statement modified report in GP and I am trying to get the
report to Page Break when it goes to next customer record, because obviouslly
I cannot have 2 customers on same page.

So I created a additional footer in Section Options and set it to Page Break
on Customer Number.

That is working fine, it does page break when customer record changes. But
when I have a customer that has 2 pages worth of invoices listed, on the 2nd
page header it will list the Name of the following customer. Why is that?

For example, I have a customer called ABC and XYZ. It will print the 1st
page with ABC and 2nd page even though it still is listing documents/invoices
for Customer ABC will for some reason display name of Customer XYZ at the
top.

Do anyone have any ideas or tips on how to fix this? I'm pretty confident
I've got the break setup correctly, I just don't know why its displaying name
of next Customer record on page header, even though it technically is still
listing documents for the current customer.

David Musgrave [MSFT]

unread,
Oct 2, 2008, 5:20:14 AM10/2/08
to
I have seen something similar before and it was not fixable without using VBA.

The situation I had was a document that could fix x number of lines on a page. We had a footer which contained a sum.

If we had enough records to just push the footer to the next page but any of the records, a customer name in the page header would
show the next customer. If at least one record for the current customer prints on the second page, the customer name would be
correct.

I will try and explain what is happening.

The Report Writer is a single pass report writer and runs through the data from top to bottom once.

When a footer is printed, the current record pointer has already moved to the first record of the next customer. That's why footers
need to use the Last Occurance setting.

If we print a page header with the type of data it will printer the current record which is already the next customer.

David Musgrave [MSFT]
Escalation Engineer - Microsoft Dynamics GP
Microsoft Dynamics Support - Asia Pacific

Microsoft Dynamics (formerly Microsoft Business Solutions)
http://www.microsoft.com/Dynamics

mailto:David.M...@online.microsoft.com
http://blogs.msdn.com/DevelopingForDynamicsGP

Any views contained within are my personal views and not necessarily Microsoft policy.
This posting is provided "AS IS" with no warranties, and confers no rights.

DynamicsGonePartying

unread,
Oct 2, 2008, 5:58:15 PM10/2/08
to
David,

Thanks for your very helpful explaination for the reason behind this issue.
To me it sounds like it would be considered a minor "glitch" or "bug" with
Report Writer.

Since I am not a developer and know nothing about VBA, I had to take another
approach to solving this problem.

What I did was I removed Customer Name & Address from "page header" and only
left that information on "report header". I then went into section options
and changed the option from "page break" to "reset report".

By doing this, only the 1st page of statement would print Customer name &
info per customer. This resolved my issue because as mentioned on the last
page the Customer name & address was printing information of the next
customer record.

Luckily, my manager/CFO was cool with my fix, so I did not need to scramble
around to find VBA code, but that would be handy to have somewhere on the
forums.

Thanks again for your input....Cheers mate.

David Musgrave [MSFT]

unread,
Oct 8, 2008, 1:01:11 AM10/8/08
to
You can also use an Additional Header with break on Customer ID, but this will not repeat the current customer when there is a page
break.

Well done for finding a solution that worked for you.

David Musgrave [MSFT]
Escalation Engineer - Microsoft Dynamics GP
Microsoft Dynamics Support - Asia Pacific

Microsoft Dynamics (formerly Microsoft Business Solutions)
http://www.microsoft.com/Dynamics

mailto:David.M...@online.microsoft.com
http://blogs.msdn.com/DevelopingForDynamicsGP

Any views contained within are my personal views and not necessarily Microsoft policy.

This posting is provided "AS IS" with no warranties, and confers no rights.

0 new messages