cninghm
asked on
suppressing page break on last item in group - access report
Hi Experts:
I have a report with multiple breaks. For simplicity sake, I'll keep the question refined to three breaks:
Group Header
Location Header
Plan Header
Plan Footer (new page)
Location Footer (new page)
Group Footer (Group totals > inserted page break > fancy page finalizing group)
My problem: When the last Location comes in for the Group, I don't want a page break. I want the Group totals to appear directly under the location totals, then, the inserted page break will take care of printing the fancy page all by itself. How do I prevent the final Location within the group from breaking a page? Is there an event that the last Location will trigger that I can interrogate?
e.g., If Location.Last_Record = true then
else new page
Thanks,
Betty
I have a report with multiple breaks. For simplicity sake, I'll keep the question refined to three breaks:
Group Header
Location Header
Plan Header
Plan Footer (new page)
Location Footer (new page)
Group Footer (Group totals > inserted page break > fancy page finalizing group)
My problem: When the last Location comes in for the Group, I don't want a page break. I want the Group totals to appear directly under the location totals, then, the inserted page break will take care of printing the fancy page all by itself. How do I prevent the final Location within the group from breaking a page? Is there an event that the last Location will trigger that I can interrogate?
e.g., If Location.Last_Record = true then
else new page
Thanks,
Betty
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Jeff:
On the "Group" thing. I agree, but it's an inherited nightmare and I have limited time (no time to re-design).
On the posting example, I cannot - confidentiality.
I'm working with users to convince them of alternative design in report. Thought it might be something simple.
I will keep your suggestion in mind and get back to you.
Thanks,
Betty
On the "Group" thing. I agree, but it's an inherited nightmare and I have limited time (no time to re-design).
On the posting example, I cannot - confidentiality.
I'm working with users to convince them of alternative design in report. Thought it might be something simple.
I will keep your suggestion in mind and get back to you.
Thanks,
Betty
<On the posting example, I cannot - confidentiality.>
See steps 8.
I only need a database that *Replicates* the issue...
See steps 8.
I only need a database that *Replicates* the issue...
ASKER
Jeff:
The users are ok with 3 blank lines between breaks instead of page break. I accepted your solution since I believe it would work if they insisted on the break.
Thanks,
Betty
The users are ok with 3 blank lines between breaks instead of page break. I accepted your solution since I believe it would work if they insisted on the break.
Thanks,
Betty
ok
Enjoy the weekend
Enjoy the weekend
ASKER
You too, buddy!
Can you post a simple sample of the DB
Also note that using a Group called "Group" is confusing...
Sample database notes:
1. Back up your database(s).
2. Combine the front and back ends into one database file.
3. Remove any startup options, unless they are relevant to the issue.
4. Remove any records unless they are relevant to the issue.
5. Delete any objects that do not relate directly to the issue.
6. Remove any references to any "linked" files (files outside of the database, Images, OLE Files, ...etc)
7. Remove any references to any third party Active-x Controls (unless they are relevant to the issue)
8. Remove, obfuscate, encrypt, or otherwise disguise, any sensitive data.
9. Compile the code. (From the VBA code window, click: Debug-->Compile)
10. Run the compact/Repair utility.
11. Remove any Passwords and/or security.
12. If a form is involved in the issue, set the Modal and Popup properties to: No
(Again, unless these properties are associated with the issue)
13. Post the explicit steps to replicate the issue.
14. Test the database before posting.
In other words, ...post a database that we can easily open and immediately see and/or troubleshoot the issue.
And if applicable, also include a clear graphical representation of the *Exact* results you are expecting, based on the sample data.
JeffCoachman