Mail Merge won't print signature

How is the signature inserted into the document?

Does the merge document itself print OK?

Set Word not to print in background mode and you may have more success.

If the data is Excel, see if you fare any better with http://www.gmayor.com/ManyToOne.htm  in One to One mode. This uses a different process from mail merge. If the merge document prints OK, then so should this.

When used in one to one mode, you can use any field as the key field that does not have the same data in consecutive records in the chosen field. The process creates a new document every time the record value in the 'key' field changes.

The hash sign '#' however cannot be used in the data as it is used in the process. If you really want a pound sign "£" then that can be used. # is often used to represent 'No.' or 'Number'. In such a case use 'No.'  instead.

Without examining the document I cannot determine why it does not work when merged conventionally. Clearly there is some issue with the graphic. You could try saving as Word 97-2003 DOC format as this uses a different graphics engine.

You might try the Merge to Individual Documents utility on the MergeTools – 20140218.dotm Add-in that I created that can be downloaded from the following page of my One Drive:

http://bit.ly/1hduSCB

I don't think that it has an issue with the # character being used in the data (as distinct from in the name of one or more of the fields in the data source).

The file needs to be saved in the Word Startup folder.  In Windows XP the default location for that folder is

C:\Documents and Settings\[User Name]\Application Data\Microsoft\Word\STARTUP

In Windows Vista and Windows 7, 8 or 8.1 it is

C:\Users\[User Name]\AppData\Roaming\Microsoft\Word\STARTUP

When that has been done and Word is started\re-started, the tab shown below will be added to the Ribbon:



One thing to note is that the field names in the data source must contain only alphanumeric characters (No @,#,$,%,&,(,), etc) and the field names must not start with a numeric character (0-9).

You can substitute https://dl.dropboxusercontent.com/u/57986755/ManyToOneMailMerge%20Ver%208.3.dotm for the version in the zip file on my web site. This one doesn't have the # check. Do however see the readme in the ZIP from my web site.

# in the field names is less important as that is trapped by the add-in.

You probably don't need a special key field. You just need to declare any field that doesn't have the same data in consecutive records as the key. The fact that the field may have the same data later in the column doesn't matter.