Publisher does not suppress blank fields with Catalog Merge...please help

[Justme]

As I originally posted, I need help finding out why Publisher is not
suppressing blank lines when I merge to a new (or existing) document.
[I tried to reply to the existing post, but google just gave me an
error.]

The person who replied just referred me to the help file (F1). Well,
actually, I have tried the Help file, Microsoft's knowledge base, and
newsgroups. That's why I posted here. I cannot find any information
as to why it is not suppressing blank fields, and inserting extra
lines.

Some real constructive help would really be appreciated. I am posting
here as a last resort, because I have searched everywhere else.

Thank you to those that do have helpful ideas.

Lin

----------------------------------------------
I set up a Catalog Merge document. The main document looks fine. Any
blank lines are not appearing. Everything looks great. (addresses)

I then Merge to a New document and I also tried merging to an existing
document. When I do, all of the blank lines show up. So now there
are spaces between lines where I don't want them. And, it's a large
database, so it would take a long time to delete all the extra lines.

I cannot find any option to suppress blank lines, expect in the main
document print merge, but I don't want to do a print merge.

Anyone have an idea of what I am missing or what I could try?? I'm
using Publisher 2003 with WinXP home.

Thanks,

Lin

 

[°°°MS°Publisher°°°]

When you go to PRINT there is a dialogue box that says:
Don't print lines that contain only empty fields.
Check that dialogue box and away you go - up Up UP in the air

 

[Ed Bennett]

A small child turns to Ed, and exclaims: "Look! Look! A post from

When you go to PRINT there is a dialogue box that says:
Don't print lines that contain only empty fields.
Check that dialogue box and away you go - up Up UP in the air

If you read the existing post rather than making up what you think he should
have said, you will see that he doesn't want to use the Print Merge, he
wants to merge to an existing publication, and can't see how to avoid blank
lines when doing this.

 

[°°°MS°Publisher°°°]

Well you have to print somehow at sometime otherwise what use is the
document?
If you read the HELP file it tells you there is no way to do that other than
'fill the lines or sort the database accordingly' or some garbage like that.

 

[Ed Bennett]

A small child turns to Ed, and exclaims: "Look! Look! A post from

Well you have to print somehow at sometime otherwise what use is the
document?

*<pbhtu>* OHYYFUVG! *</pbhtu>*

 

[Brian Kvalheim - [MS MVP]]

In

A small child turns to Ed, and exclaims: "Look! Look! A post from


*<pbhtu>* OHYYFUVG! *</pbhtu>*

Sounds like a good bug though

--
Brian Kvalheim
Microsoft Publisher MVP
http://www.mvps.org/publisher

This posting is provided "AS IS" with no warranties, and
confers no rights.

 

[Justme]

Okay. I'll add more information than what "donotknock" seems to
understand. Two points:

1) When you merge a Catalog to a new document, it is *no longer
linked to the database*. Hence, when you go to the Print dialog box,
there is no option to print or not to print blank fields. This option
is only available from the Original "template" that you create before
you merge to a New or existing document.

2) I do not want to print before I merge. I want to create a
Directory (Catalog), put page numbers, graphics, etc. When you do a
Catalog Merge using the Catalog Merge Wizard, it ends asking you if
you want to merge to a New document or an Existing document...it DOES
NOT ask you if you want to print!! (I know I can print by using print
command, and I'm sure if I did it would suppress the blank fields.) I
want to create a NEW document with all the information saved in that
new document. I don't want to have to print it everytime I need the
information.

By the way, using Word 2003 Mail Merge Directory Wizard, you can merge
to a new or existing document and Word does suppress blank lines. I
just wanted to be able to do the project in Publisher, not Word. (I
do know how to get it done in Word and transfer it to Publisher. I
just don't understand why Publisher's Merge will NOT suppress blank
fields (and inserts lines for the blank fields).

Say is Kevin Kvalheim around???

Thank you,
Lin

 

[Brian Kvalheim - [MS MVP]]

In

Okay. I'll add more information than what "donotknock" seems to
understand. Two points:

1) When you merge a Catalog to a new document, it is *no longer
linked to the database*. Hence, when you go to the Print dialog box,
there is no option to print or not to print blank fields. This option
is only available from the Original "template" that you create before
you merge to a New or existing document.

2) I do not want to print before I merge. I want to create a
Directory (Catalog), put page numbers, graphics, etc. When you do a
Catalog Merge using the Catalog Merge Wizard, it ends asking you if
you want to merge to a New document or an Existing document...it DOES
NOT ask you if you want to print!! (I know I can print by using print
command, and I'm sure if I did it would suppress the blank fields.) I
want to create a NEW document with all the information saved in that
new document. I don't want to have to print it everytime I need the
information.

By the way, using Word 2003 Mail Merge Directory Wizard, you can merge
to a new or existing document and Word does suppress blank lines. I
just wanted to be able to do the project in Publisher, not Word. (I
do know how to get it done in Word and transfer it to Publisher. I
just don't understand why Publisher's Merge will NOT suppress blank
fields (and inserts lines for the blank fields).

Say is Kevin Kvalheim around???

It's Brian Kvalheim

I am here, and this is a confirmed bug that we have just added to the
Publisher database. I will supply more info if I get more.
--
Brian Kvalheim
Microsoft Publisher MVP
http://www.mvps.org/publisher

This posting is provided "AS IS" with no warranties, and
confers no rights.

 

[Justme]

In

It's Brian Kvalheim

I am here, and this is a confirmed bug that we have just added to the
Publisher database. I will supply more info if I get more.

Oops!! Sorry, Brian! I was tired when I wrote that (and, a bit
exasperated with "donotknock!").

And, THANK YOU! For at least confirming that there is a bug. Wish
there was a work around. What do they usually do with confirmed bugs?
Do they make patches for things like this? It seems to put a big
hole in the functionality of Catalog Merge (not all records have data
in all fields).

thanks again,
Lin

 

[Brian Kvalheim - [MS MVP]]

Oops!! Sorry, Brian! I was tired when I wrote that (and, a bit
exasperated with "donotknock!").

And, THANK YOU! For at least confirming that there is a bug. Wish
there was a work around. What do they usually do with confirmed bugs?
Do they make patches for things like this? It seems to put a big hole
in the functionality of Catalog Merge (not all records have data in all
fields).

Lin,

If they address this, they wouldn't look at it until a future version
of Publisher, not in a patch. --
Brian Kvalheim
Microsoft Publisher MVP
http://www.mvps.org/publisher

This posting is provided "AS IS" with no warranties, and confers no rights.