creating a church directory in publisher 2003, using data from acc

Am trying to catalog merge a query created in access to create a church
directory. The snag I'm hitting has to do with keeping the records for a
particular family from being printed in the next listing(there's 2 families
per page). I had to use subforms in access in order to input the variable
number of children names and birthdays. In doing so, the member's name and
record number had to remain the same while the children's names and record
numbers kept incrementing. Kinda scratching my head on this one. Any help
would be appreciated. I'm almost positive the database is sound, just a
matter of getting it read into publisher in a manner that it can better be
manipulated. Perhaps a macro?

Is there no one who can help me with this? My wife's gonna kill me if I
don't come through with this.

"AC-Donace" wrote:

Am trying to catalog merge a query created in access to create a church
directory. The snag I'm hitting has to do with keeping the records for a
particular family from being printed in the next listing(there's 2 families
per page). I had to use subforms in access in order to input the variable
number of children names and birthdays. In doing so, the member's name and
record number had to remain the same while the children's names and record
numbers kept incrementing. Kinda scratching my head on this one. Any help
would be appreciated. I'm almost positive the database is sound, just a
matter of getting it read into publisher in a manner that it can better be
manipulated. Perhaps a macro?

Maybe this will be helpful.
Catalog merge
http://office.microsoft.com/en-us/pu...504381033.aspx

Have you tried converting your merge to a publication in step 5? You would be
able to manipulate the fields.


--
Mary Sauer MSFT MVP
http://office.microsoft.com/
http://msauer.mvps.org/
news://msnews.microsoft.com

"AC-Donace" wrote in message
...
Is there no one who can help me with this? My wife's gonna kill me if I
don't come through with this.

"AC-Donace" wrote:

Am trying to catalog merge a query created in access to create a church
directory. The snag I'm hitting has to do with keeping the records for a
particular family from being printed in the next listing(there's 2 families
per page). I had to use subforms in access in order to input the variable
number of children names and birthdays. In doing so, the member's name and
record number had to remain the same while the children's names and record
numbers kept incrementing. Kinda scratching my head on this one. Any help
would be appreciated. I'm almost positive the database is sound, just a
matter of getting it read into publisher in a manner that it can better be
manipulated. Perhaps a macro?

Thank you for your response, Mary. I think I used the proper procedures for
setting up the merge and all. In Access, I started out with 2 tables, a
member table that had the member's name, addressId(which is the autonum
field), address, phone, spouses name, etc. Then I set up a second table for
the family part, child's name, date of birth, childId(which is the autonum
field). I noticed in Publisher, it required a single table for input in a
catalog merge, so I found out how to do a query. It worked (near as I can
tell). Only thing is, in order for all the children to get read for a
particular family, it also reads the parent info along with it. So, by the
time I get all my kids(3) in, it's read the parent info 3 times. And when it
goes to input the data in the Publisher document, it takes each record and
places it in a different family listing. What I need it to do is to stay on
one address field until it reads all the kids' records, prints the info, and
then moves on to the next addressId number. That's why I was wondering if a
macro might be the ticket. You know, perhaps something like: while
addressId=? do this.....? Am I on the right track?

"Mary Sauer" wrote:

Maybe this will be helpful.
Catalog merge
http://office.microsoft.com/en-us/pu...504381033.aspx

Have you tried converting your merge to a publication in step 5? You would be
able to manipulate the fields.


--
Mary Sauer MSFT MVP
http://office.microsoft.com/
http://msauer.mvps.org/
news://msnews.microsoft.com

"AC-Donace" wrote in message
...
Is there no one who can help me with this? My wife's gonna kill me if I
don't come through with this.

"AC-Donace" wrote:

Am trying to catalog merge a query created in access to create a church
directory. The snag I'm hitting has to do with keeping the records for a
particular family from being printed in the next listing(there's 2 families
per page). I had to use subforms in access in order to input the variable
number of children names and birthdays. In doing so, the member's name and
record number had to remain the same while the children's names and record
numbers kept incrementing. Kinda scratching my head on this one. Any help
would be appreciated. I'm almost positive the database is sound, just a
matter of getting it read into publisher in a manner that it can better be
manipulated. Perhaps a macro?

Have you thought of doing a merge into Word instead of into Publisher?
That's what we do for our church directory.



"AC-Donace" wrote in message
...
Is there no one who can help me with this? My wife's gonna kill me if I
don't come through with this.

"AC-Donace" wrote:

Am trying to catalog merge a query created in access to create a church
directory. The snag I'm hitting has to do with keeping the records for a
particular family from being printed in the next listing(there's 2
families
per page). I had to use subforms in access in order to input the
variable
number of children names and birthdays. In doing so, the member's name
and
record number had to remain the same while the children's names and
record
numbers kept incrementing. Kinda scratching my head on this one. Any
help
would be appreciated. I'm almost positive the database is sound, just a
matter of getting it read into publisher in a manner that it can better
be
manipulated. Perhaps a macro?

I'd really like to knock this out in Publisher. Our church uses it to
create the directory every year and it really looks nice. Thing is, the file
that's generated by it, using their method is in excess of 500 megs. I'm
convinced a database is the ticket for collecting the data and a catalog
merge is the way to go for bringing the database into Publisher. So, let's
try a different tack. Is there a way(maybe visual basic) to start reading
records in, print the member info, keep reading records while the member
number is the same(this would be one record for each child of this member),
print that child's info. Then when the member number increments, go to the
next catalog section for the next member. There's gotta be a way to do this,
right? Please, somebody tell me I'm not delusional!

"BK" wrote:

Have you thought of doing a merge into Word instead of into Publisher?
That's what we do for our church directory.



"AC-Donace" wrote in message
...
Is there no one who can help me with this? My wife's gonna kill me if I
don't come through with this.

"AC-Donace" wrote:

Am trying to catalog merge a query created in access to create a church
directory. The snag I'm hitting has to do with keeping the records for a
particular family from being printed in the next listing(there's 2
families
per page). I had to use subforms in access in order to input the
variable
number of children names and birthdays. In doing so, the member's name
and
record number had to remain the same while the children's names and
record
numbers kept incrementing. Kinda scratching my head on this one. Any
help
would be appreciated. I'm almost positive the database is sound, just a
matter of getting it read into publisher in a manner that it can better
be
manipulated. Perhaps a macro?