[AccessD] Interleaving two reports

[Ryan W]

Hey all,

So sorry I've been quiet on the topic. Weird week at work.

For now, because of the header differences between the reports I decided to
use some looping code to use the existing reports to interleave.

Basically building a recordset for each report ID and opening the report
hidden with a WhereStatement to limit it by ID, using DoCmd.OutputTo PDF
with the ID name and date so the files land in the right order in File
Explorer.

Once everything is exported the user can select all PDFs and right click ->
Combine with (Pdf Editor).

So far it works just as requested.  If I get a chance to rebuild a main
report with multiple subreports with their own respective page headers (if
I remember right you make a custom group "=1") so that it shows on each
page since page header don't work in subreports (going off memory).

So far the user who primarily hand interleaves these reports is excited to
use this new method next time.



On Sun, Jan 22, 2023 at 8:11 AM Rocky Smolin <rockysmolin2 at gmail.com> wrote:

> Yes, it could be done that way. So the data for each ID would be grouped
> and the page break would occur after the data for subreport 2.
>
> r
> On Sat, Jan 21, 2023 at 11:09 PM Bill Benson <bensonforums at gmail.com>
> wrote:
>
> > Or am I wrong that ID increment yields any opportunities on the main
> report
> > to pagebreak?
> >
> > On Sun, Jan 22, 2023 at 2:07 AM Bill Benson <bensonforums at gmail.com>
> > wrote:
> >
> > > Why a page break anywhere but the bottom of the main report? Or of the
> > > first subreport and the main report?
> > >
> > > I would “ass-u-me” you only want pages to break when subreport 1 is
> > > succeeded by subreport 2, and when ID changes.
> > >
> > > On Wed, Jan 18, 2023 at 12:39 PM Rocky Smolin <rockysmolin2 at gmail.com>
> > > wrote:
> > >
> > >> I think Borge is right. That should work - main report has one field -
> > ID
> > >> -
> > >> as record source, the two reports become subreports linked by ID to
> the
> > >> main report. At the bottom of each sub-report put a page break. And
> > walla!
> > >>
> > >> Let us know if this works.
> > >>
> > >> Best,
> > >>
> > >> r
> > >>
> > >> On Tue, Jan 17, 2023 at 8:16 PM Borge Hansen <pcs.accessd at gmail.com>
> > >> wrote:
> > >>
> > >> > This is how I would approach it:
> > >> > Main report with two sup reports and grouping by ID
> > >> > Turn off headers and footers in the access report, just concentrate
> on
> > >> the
> > >> > data and the interleaving.
> > >> > Place header and footer information in a Word Template document.
> > >> > (Any other “header” info could be placed as group header)
> > >> > Add new page code after each sub report.
> > >> > Output the access report to RTF document.
> > >> > Insert RTF document into Word Template document and save as .docx
> > >> > Perform any post processing in .docx document
> > >> > Save final product as PDF document.
> > >> >
> > >> > /Borge
> > >> >
> > >> > PS depending on circumstances consider creating VBA Word macro for
> any
> > >> post
> > >> > processing that is repeatable.
> > >> > For example we have one app where the client is doing a lot of post
> > >> > processing in Word after having output the Access report to RTF. As
> we
> > >> > can’t add rich text in a paragraph and retain the rich text in a RTF
> > >> > output, the client is using our own markup code for bold, underline
> > and
> > >> > italics during text input in the Access app. Before output to RTF we
> > >> check
> > >> > that the home spun markup codes contain both the start end end code
> > (for
> > >> > example /b and /nb as start and finish for bold text within a
> > >> paragraph).
> > >> > Applying a number of Word VBA macros we clean up the whole document
> to
> > >> > present with added formatting in final Word / PDF output.
> > >> > (We have a separate Word document - holding all VBA macros that the
> > >> Acess
> > >> > app RTF report outputs are using - that we attach to the Word docx
> > >> prior to
> > >> > post processing and detach afterwards.)
> > >> >
> > >> >
> > >> >
> > >> > On Wed, 18 Jan 2023 at 12:01, Ryan W <wrwehler at gmail.com> wrote:
> > >> >
> > >> > > The reports differ in nearly every regard, there are some
> > >> commonalities
> > >> > in
> > >> > > the page headers and the page footer always just shows page N of
> NN,
> > >> > > worrying about the page footer during the interleaving process is
> > not
> > >> of
> > >> > > importance. Both page header and footers repeat on a per page
> basis
> > on
> > >> > both
> > >> > > reports.
> > >> > >
> > >> > > The number of pages per report can differ, maximum would be 99
> IDs,
> > >> > > possibly more than 99 pages if any of the detail section data
> spills
> > >> into
> > >> > > more pages with our current config.
> > >> > >
> > >> > > After I emailed this off I talked to one of the users doing the
> hand
> > >> > > interleaving and there may be a third report that is used
> depending
> > on
> > >> > > client requirements.
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > On Tue, Jan 17, 2023 at 7:46 PM Rocky Smolin <
> > rockysmolin2 at gmail.com>
> > >> > > wrote:
> > >> > >
> > >> > > > Does each page have the headers and footers repeated?
> > >> > > >
> > >> > > > Is the format of the data in the detail section of reports 1
> and 2
> > >> the
> > >> > > same
> > >> > > > or different?
> > >> > > >
> > >> > > > Is the number of pages in each of the reports the same ? Can the
> > >> number
> > >> > > of
> > >> > > > pages in the reports vary? Maximum?
> > >> > > >
> > >> > > >
> > >> > > > r
> > >> > > >
> > >> > > >
> > >> > > > On Tue, Jan 17, 2023 at 4:50 PM Ryan W <wrwehler at gmail.com>
> > wrote:
> > >> > > >
> > >> > > > > Shuffle the pages:
> > >> > > > >
> > >> > > > > Rpt 1 P 1
> > >> > > > > Rpt 2 P 1
> > >> > > > > Rpt 1 P 2
> > >> > > > > Rpt 2 P 2...
> > >> > > > >
> > >> > > > > I have the code to do and print to a PDF printer which can
> then
> > be
> > >> > > merged
> > >> > > > > quite easily, but it would be nice if I could just append each
> > >> page
> > >> > > sent
> > >> > > > to
> > >> > > > > the PDF printer to the PDF being built.
> > >> > > > >
> > >> > > > > I'll be tinkering around with Jim's idea of trying to
> interleave
> > >> the
> > >> > > data
> > >> > > > > in the report as opposed to my code loop but I didn't have
> luck
> > >> using
> > >> > > my
> > >> > > > > existing reports as subreports on a new main report (likely
> due
> > to
> > >> > > having
> > >> > > > > page headers, detail sections etc).  It only printed the first
> > >> detail
> > >> > > > > section from the first subreport and not the second subreport.
> > >> > > > >
> > >> > > > >
> > >> > > > >
> > >> > > > > On Tue, Jan 17, 2023 at 6:42 PM Rocky Smolin <
> > >> rockysmolin2 at gmail.com
> > >> > >
> > >> > > > > wrote:
> > >> > > > >
> > >> > > > > > By interleave do you mean show part of report A, then part
> of
> > >> > report
> > >> > > > B,
> > >> > > > > > then another part of report A, another part of report B,
> etc.?
> > >> > > > > >
> > >> > > > > > r
> > >> > > > > >
> > >> > > > > > On Tue, Jan 17, 2023 at 10:37 AM Ryan W <wrwehler at gmail.com
> >
> > >> > wrote:
> > >> > > > > >
> > >> > > > > > > Does anyone have any suggestions on how I can interleave
> two
> > >> > > separate
> > >> > > > > > > reports?
> > >> > > > > > >
> > >> > > > > > > They both contain data that can be grouped together by an
> > ID,
> > >> but
> > >> > > the
> > >> > > > > > > report format is different between them and at the moment
> my
> > >> end
> > >> > > > users
> > >> > > > > > are
> > >> > > > > > > printing both reports to PDF and then interleaving them in
> > the
> > >> > PDF
> > >> > > to
> > >> > > > > > > produce the desired report.
> > >> > > > > > >
> > >> > > > > > > My current thought is somehow to use DoCmd.PrintOut and a
> > >> loop to
> > >> > > > print
> > >> > > > > > an
> > >> > > > > > > alternating page range.  I just need to somehow ensure
> that
> > if
> > >> > the
> > >> > > > > report
> > >> > > > > > > per ID is more than one page that gets accounted for as
> > well.
> > >> > > > > > > --
> > >> > > > > > > AccessD mailing list
> > >> > > > > > > AccessD at databaseadvisors.com
> > >> > > > > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > >> > > > > > > Website: http://www.databaseadvisors.com
> > >> > > > > > >
> > >> > > > > > --
> > >> > > > > > AccessD mailing list
> > >> > > > > > AccessD at databaseadvisors.com
> > >> > > > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > >> > > > > > Website: http://www.databaseadvisors.com
> > >> > > > > >
> > >> > > > > --
> > >> > > > > AccessD mailing list
> > >> > > > > AccessD at databaseadvisors.com
> > >> > > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > >> > > > > Website: http://www.databaseadvisors.com
> > >> > > > >
> > >> > > > --
> > >> > > > AccessD mailing list
> > >> > > > AccessD at databaseadvisors.com
> > >> > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > >> > > > Website: http://www.databaseadvisors.com
> > >> > > >
> > >> > > --
> > >> > > AccessD mailing list
> > >> > > AccessD at databaseadvisors.com
> > >> > > https://databaseadvisors.com/mailman/listinfo/accessd
> > >> > > Website: http://www.databaseadvisors.com
> > >> > >
> > >> > --
> > >> > AccessD mailing list
> > >> > AccessD at databaseadvisors.com
> > >> > https://databaseadvisors.com/mailman/listinfo/accessd
> > >> > Website: http://www.databaseadvisors.com
> > >> >
> > >> --
> > >> AccessD mailing list
> > >> AccessD at databaseadvisors.com
> > >> https://databaseadvisors.com/mailman/listinfo/accessd
> > >> Website: http://www.databaseadvisors.com
> > >>
> > >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>