Defeat SourceObject Limitation?

[David Habercom]

I need to produce 800+ reports which can have one of 5 cover letters,
depending on the contents of a data field which identifies the author.
During collation, we need to add various inserts to individual reports, and
coordinating all the pieces requires that the letters be in alphabetical
order (by recipient.) It would be ideal to have a single alphabet, but
because Access 2000 does not permit me to use a subreport for the cover
letter and simply change its source object during printing, I have to run
the report 5 times, once for each cover letter. The result: 5 alphabets.

I am in the midst of re-coding this beast so that a form using an
alphabetical query prints one cover letter, then the remaining pages for
that recipient, then clicks to the next recipient, prints one cover letter,
and so on. Is there a better way?

Thanks.

David Habercom

 

[Marshall Barton]

I need to produce 800+ reports which can have one of 5 cover letters,
depending on the contents of a data field which identifies the author.
During collation, we need to add various inserts to individual reports, and
coordinating all the pieces requires that the letters be in alphabetical
order (by recipient.) It would be ideal to have a single alphabet, but
because Access 2000 does not permit me to use a subreport for the cover
letter and simply change its source object during printing, I have to run
the report 5 times, once for each cover letter. The result: 5 alphabets.

I am in the midst of re-coding this beast so that a form using an
alphabetical query prints one cover letter, then the remaining pages for
that recipient, then clicks to the next recipient, prints one cover letter,
and so on.

Are you sure you need 5 different subreports for the types
of cover letter? If the subreport are not too different,
you could use a single subreport with code in the
appropriate events to deal with the differences.

If worst comes to worst and you really have to have
different subreports, then you might be willing to pay the
performance penality of having all 5 subreports for every
recipient with some code to make all but one of them
invisible.