Merge field error (length field names) (2003/SP2)

[HansV]

I don't know what the maximum length is. You might try the following:

- Select Tools | Options...
- Activate the General tab.
- Tick the check box "Confirm conversion at open".
- Click OK.
- Go back to step 3 in the Mail Merge task pane.
- Click the option to select another data source.
- Navigate to the data source file, select it and click Open.
- You'll be prompted for a method to connect to the data source.
- Try one of the other options than the default OLE DB.
- Proceed as usual.

I'd guess that the original field names in the data source contain spaces. In general, I would recommend against using spaces in field names (and to keep field names short).

[leecol]

Edited by HansV to replace attached Word document with the picture it contained - saves the reader a few clicks

Whilst upgrading from Word 2000 to Word 2003 we have encountered errors when merging documents. It only occurs on merge fields that have a long name. We get an error saying invalid merge field with the field name listed (example attached). The shorter names work okay. Does anyone have any idea of what the field lenth is, how many characters, or how to work around merging fields with longer names. The only alternative I have at the moment is to place users back on Word 2000.

[leecol]

Thanks for your reply Hans. I forgot to mention that it is not the typical mail merge data source but we have an interface that creates a new data source every time a precedent is run and the fields are taken from a SQL database. When I open a precedent to edit fields it is not actually attached to the data source until it is run from our interface.

[leecol]

We have now worked out the maximum field length is 38 characters after the words MERGEFIELD. Why the longer fields work with Word 2000 but not Word 2003 I do not know.

[HansV]

Thanks for the update, it's good to know.