CatBlue said:
Thank you for your replies. Ed, your reply did confuse me a bit. If
what I see in Outlook is not what is communicated to mail merge,
aren't you saying essentially that the Outlook engine and the mail
merge engine don't speak the same language (hence my term "not
playing well with others)?
No. Publisher's Mail Merge communicates with a standardised data engine in
a standard manner.
I think (although am not an expert on Outlook, so cannot say for sure) this
data engine then communicates with your Outlook files to get at the Contact
database. Outlook has saved this in a proprietary way, and when it is
running, the field names on the screen do not necessarily correspond to
field names in the actual database.
It is confusing, but basically it's Outlook's fault.
Again, it's a bit confounding to me that
these are all programs created within the Microsoft Office Suite, and
yet they don't work together seamlessly. To get what you need done
you need to know certain tricks.
It's a nice ideal, but it's rather impractical. Each program has thousands
of features, and it's a difficult enough task to get them to work how the
majority of users want within the program. To then make them work perfectly
interoperably every other program increases the workload exponentially. In
this case, to make the Outlook Contacts merge work correctly within
Publisher (or another standard database), it may have a negative impact on
the appearance of the Contacts within Outlook itself, or it may just take a
lot of additional development time (which could have productively been spent
on improving other areas of the product which would affect more users).
e.g. Users with Outlook = A very large number
(Users who use Outlook = A slightly smaller, large number)
Users with Publisher = A middle-sized number
(Users who use Publisher = A smaller middle-sized number)
Users with Outlook AND Publisher = A relatively small number
(Users with Outlook AND Publisher who use both = A smaller number)
(Users with Outlook AND Publisher who use Mail Merge = An even smaller
number)
(Users with Outlook AND Publisher who use Mail Merge with their Outlook
contacts = A very small number)
Fixing the Mail Merge from Publisher would affect a very small number of
users. Spending the development time on a global feature would affect a
large number of users.
But I digress. Since this is the group for discussing Publisher, I do
have a final query. Why was I only able to complete this merge when I
started in Outlook and then chose the postcard created in Word? When I
tried to choose the Publisher document I thought Publisher would open
automatically like it did with the Word document. Instead, I was
brought to a page in Word filled with hieroglyphics. It seems a shame,
because creating and redesigning the postcard in Publisher was much
easier than working in Word, IMO.
It is a shame, but this is the way Outlook works.
(Caveat: I've never used Outlook for a mail merge)
It sounds like Outlook is simply invoking Word to open the document in
question. It is specially-programmed to do some jiggery-pokery in Word to
make the document merge correctly. You get heiroglyphics because that is
how Word sees a Publisher file. To do the same with Publisher would require
a lot of work (see the problem described above), probably more than it did
to make it work with Word (due to the different way Publisher works).