Re: Migrating from Word mail merge to Access Reports

John, thanks for the reply but I just ran a test by creating two of the
packet pages as separate subreports and putting to subreport controls in one
master report. The CanGrow works fine but it still prints all clients'
"page 1" followed by all clients "page 2". Maybe I missed something about
your advice that would have resolved that?

Thanks again,

Anth


"John Spencer" <spencer@xxxxxxxxx> wrote in message
news:%23Kb3SZTXIHA.4696@xxxxxxxxxxxxxxxxxxxxxxx
A report Section is limited to 22 inches in height
A report is limited to 200 inches in height
A sub-report put onto a report can grow.

SO,
Add a group to your report based on the client id and put some of your
controls in the group header and footer and some in the details section.
You can add another group based on the clien id to get an additional 44
inches of print space.

So with two group headers, two group footers, and a detail section you
should be able to get 110 inches of printing space.

Another option is to sub-divide your data into some sub reports and then
set the height of the sub-report controls to .5 inches or less with a page
break control between each sub-report. Turn on Can Grow for the
sub-reports and the section containing the sub-reports.

Hopefully this will give you some ideas on overcoming the 22 inch limit of
a section in a report.


--
John Spencer
Access MVP 2002-2005, 2007-2008
Center for Health Program Development and Management
University of Maryland Baltimore County
.

"Anthony Stever" <anth@xxxxxxxxx> wrote in message
news:O9afzfSXIHA.4476@xxxxxxxxxxxxxxxxxxxxxxx

Hi folks,

I'm trying to help convert a fairly cumbersome MS Word<>MS Access mail
merge process to an "all Access" solution. The office has several
packets for clients that consist of 8-10 pages each of printed info that
is customized to the clients' own info via a typical mail merge.
However, the process keeps breaking, especially in terms of having to
re-establish the link from the main document to the data source and then
filter it for the right clients.

My thought was to move this to Access, create a form to filter the
records in an easier fashion than having someone manually look through
the record list (using a form for criteria) and then producing however
many packets are needed, fully "merged" and so on. For example...

pg 1 Client Encounter Form
pg 2 Client Action Items
pg 3 Office Information and Next Appointment
... and so on for 8-10 pages.

I thought I'd put all of pages of one packet into one report and end up
with 3 separate reports, one for each 8-10pg packet. That's when I
bumped into the 22" vertical size limit for an Access report.

My next thought was to make each page a separate report, which I could do
easily enough but then we end up having someone on staff having to
collate the packets. That is, I had thought about using a macro to
print each of the reports in succession and that's what leads to someone
having to collate the packets (i.e. print report 1 for 10-100 people,
then print report 2 for 10-100 people and then someone has to go through
2 x 10-100 print jobs and add report 1 to report 2 for person 1, then add
report 1 to report 2 for person 2, etc.)... because I don't know of a way
in Access to make it "perfect".

Am I stuck with that trade-off vs. living with the dysfunctional system
or are there other options I haven't considered?

Thanks in advance!

Anth






.

Relevant Pages

  • Migrating from Word mail merge to Access Reports
    ... I'm trying to help convert a fairly cumbersome MS WordMS Access mail merge ... to the clients' own info via a typical mail merge. ... list and then producing however many packets are ... the 22" vertical size limit for an Access report. ...
    (microsoft.public.access.reports)
  • Re: select column name base on users choice
    ... definition at runtime so that its controls are bound to the selected columns. ... In fact you are going to have to amend the report definition anyway, ... But this will only store the query in a string, ...
    (microsoft.public.access.queries)
  • Re: Microsoft has utterly failed with Access 2007
    ... Access 2003 already included grouped controls. ... if I have a typical report with a line of details ... property sheet opening ... In other words again the keyboard choices and general design of access 2007 ...
    (microsoft.public.access.modulesdaovba)
  • Re: MS Access Reports and VB.NET Program
    ... think that I want to ship a 30mb .NET framework to each of my clients? ... Barns & Noble has some books that could help you learn .NET. ... It is Access TIMES eCommerce TIMES Sql Server. ... that you actually posted how to execute the report using a macro. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Summarizing records in one table that match a different table
    ... the report. ... using "Language" as the example (i had to add a field to my Clients test ... i created a report based on the query with the joins ...
    (microsoft.public.access.reports)