Office.Word 2003. mailmerge Create a field string for a greeting l

Similar Threads:

1.Word 2003 MailMerge Field Formatting

I have a Word document with mail merge fields.  I set the Field Properties: 
Format to "First capital" on each field.  However, when Word performs the 
mail merge, the formatting is lost and all of the data comes in with capital 
letters.

The data is coming in from an Access query and the data is stored in all 
uppercase.  Is there a way I can tell Word to ignore the formatting of the 
incoming data?

Thanks,

-- 
Steve Commisso
Consultant
Software Architects, Inc.

2.Office 2003 Mailmerge in word 2003

Hi Beth,
Thanyou for your reply
Yes it is the windows installer screen that appears. It is the main mailmerge  document that is launched, the data source is a text file where the header information and data are combined, also the field seperator is a comma

Regards

Lewis(TheITguy)


"Lewisi" wrote:

> Hi there,
> When I do a mailmerge in Word 2003 it first shows the insallation screen and then take a very long time to open the merge document 2 - 3 Mins typ.
> Can anyone help

3.BCM Mailmerge won't do nickname greeting?

I created an email message in Word that I want to use for an email BCM 
Marketing Campaign. The greeting line is Dear <<Nickname>>, using the 
nickname field under Insert Merge Field command in the word Mailings ribbon.

When I try to run the campaign I get this error message: "Invalid Merge 
Field: This field is used in the main document, but does not exist in the 
data source."

I have verified that there is data in the nickname field for the selected 
contact in BCM.

How  do I fix this? 

4.Office 2003 Word mailmerge with Access

I have recently converted an Access database and associated Word merge 
documents from Office 97 to Office 2003.

It has generally gone well, but I now find that from Word 2003 that only 
some, but not all, of the queries in the associated Access 2003 database are 
visible, when trying to reset the source as a query in the new version of the 
database.

There is a database workgroup file which Access has joined, and the user has 
all permissions on ALL queries - we don't see any differences between the 
queries which can be seen and those which cannot in this respect..

When the Word document is opened, there is no request to sign on as there 
used to be in the old version - I don't know if this is relevant.

How can I make sure that ALL queries are visible as potential word data 
sources?

-- 
Jon

5.Word maximum no of fields in MailMerge

We have encountered an interesting issue when doing stress testing on
an Add-In that we have developed.  Its an Add-In written in Delphi and
has been working fine with Word in the past.  Recently, as a result of
some stress testing on a new version of our Add-In by a client, we
were told that after they had selected 37 mail merge fields for a
document to be merged, they were getting strange errors including an
OLEException 'String is longer than 255 characters'.

I did some research on this and found others who had experienced
similar issues.  It appears to be due to the way that Word works when
the datasource used for a Mailmerge is internal to MS Word.  What I
noticed is that when we prep our data to be the datasource for a Word
merge, it basically takes it and creates a table of the data (I'm
testing this in Word 2003 but it appears to act the same in Word
2007).  When fewer fields are used in a merge, the table is created
correctly and the merge succeeds.  But when we hit these higher
numbers, the tables will not create, and therefore attempting to use
that data as the data source causes error dialogs in Word relating to
'Invalid Headers' or something like that.  Clearly the datasource is
the culprit.

What I'm trying to determine is what defines the upper boundaries for
internal datasources for Word merge?  We are only ever merging with
one row in there, but the number of columns can be high.  Is this
measured in terms of byte size, or number of columns, etc.?  Some of
the tests we have encountered appears to allow up to 44 columns, but
it depends on what columns were selected for the merge, and/or the
size of the data being merged.

I'd certainly appreciate anyone with some experience in these upper
limits to chime in on this.

Thanks
Myles

6. MailMerge - custom fields not available in Word

7. Using Automation to open Word and create mailmerge document and then Print

8. Outlook 2000 - emails created by MailMerge from Word