Rick A <allisonrja@hotmail.com> was very recently heard to utter:
> I just started. I set up a data source to a simple query at this
> time. I do see your point that it might not allow two or more
> sources.
You have to write a script to do the first merge from one source, then the
second merge from the second source, attaching to the end of the publication
made by the first merge.
> I am also concerned that the "text box" created by catalog merge
> cannot grow. While I want to repeat the input , what I have varies
> from two line to six lines and I do not want to have all that extra
> white space in the catalog. Any thoughts on that?
That requires manual tweaking. Is it likely that the extra space gained
from removing four lines every so often would allow you to fit one extra
line per page? Otherwise, you'll simply be displacing the whitespace to the
bottom of the page, where it would be more unsightly.
The only way to automatically do this would be to bypass Publisher's Catalog
Merge and construct your own merge scripts manually.

Signature
Ed Bennett - MVP Microsoft Publisher
Rick A - 18 Feb 2006 01:51 GMT
Ed,
Do you know of any samples showing how to construct a merge script? I learn
so much faster when I can start with an example to get started and grow from
there.
I'm thinking that catalog merge will be too limiting for me.

Signature
Rick Allison
> Rick A <allisonrja@hotmail.com> was very recently heard to utter:
>> I just started. I set up a data source to a simple query at this
[quoted text clipped - 17 lines]
> The only way to automatically do this would be to bypass Publisher's
> Catalog Merge and construct your own merge scripts manually.
Ed Bennett - 18 Feb 2006 23:59 GMT
Rick A <allisonrja@hotmail.com> was very recently heard to utter:
> Do you know of any samples showing how to construct a merge script? I
> learn so much faster when I can start with an example to get
> started and grow from there.
Nope, you'll have to piece bits together.
If you're automating straight from Access, you might not need the data
access scripts, just a publication construction script. It's pretty
autonomous coding once you've worked out exactly where you want all your
objects positioned relative to each other in each catalog box. You just
have to code in all those objects and positions, add an offset for each
subsequent item, and fill in the data. (Plus housekeeping tasks such as
keeping track of when you reach the end of a page, taking a new page when
you start a new subreport, etc etc.)
Nested loops are how I would do this.

Signature
Ed Bennett - MVP Microsoft Publisher
Rick,
No such luck here. I haven't had much time to work on it since I
posted, but I will give some of Ed's recommendations a try and let you
know what I get. I think this is going to be a bit more difficult than
it would seem. I have to check out my relationships and see if I can
manipulate them to make the subreports more transparent.
Thanks,
Craig