asked on

Word Merge Field Keeps Changing Format

I am using a mail merge wizard within the Raiser's Edge database. The merge wizard is conditional upon one field and a letter template is set up for each value in the letter field. There are six separate letters. The format is perfect in 5 of the 6 letters.

The merge field is a receipt number field that sits within table cell within the Word document. ALL letters are based on the same template. The field is formatted in each letter as Calibri 11. In 5 of the letters, the field comes out in Calibri 11. However, for the 6th letter condition, the receipt number comes out in Tahoma 8. I have tried using the MERGEFORMAT and charformat switches with no luck whatsoever. In fact, when I tried the MERGEFORMAT switch, the field value completely disappeared.

I have removed this letter and have started from scratch and it just keeps happening with this particular letter code.

This is a database that is hosted through a Citrix server so I can't access the Normal file.

Does any one have any ideas that I can try? I have been leaving this and coming back to it for the better part of a month and really need to figure out what is going on.

Thank you in advance for any help provided :)

Serena Hsi

Have you considered that the field format of the Word document may be the culprit rather than the mail merge process from Word? Typically the Normal.dot file is part of your Office install (wherever it is installed). Are you able to make a copy of the letter template and edit the form fields?

GrahamSkan

I think you will need to post enough of the mail merge main document to show us the problem. Clear all confidential or surplus text and fields and post what is left (if it still shows the behaviour).

rporter45

ASKER

Hi There

I have attached three files with all confidential information removed. The file named SFA-CR Template is the template where the issue resides. In the bottom portion, the Receipt_Number field is the field we are looking at.

This merge is a conditional mail merge using a Mail Merge Wizard and it uses the first document in the merge for page setup. The CAA-CR Template is the first letter in the merge. It also does not have an issue with the font changing for the receipt number field.

I have also attach the final merged document so that you can see the issue in it's final stage.

Please let me know if you need any other information about this.

Thanks!
SFA-CR-Template.docx
CAA-CR-Template.docx
TEST-Receipts.docx

GrahamSkan

Thanks. I have the documents open. How is the merge conditional?

rporter45

ASKER

There is a built in mail merge wizard in the database where we pick the condition and then add the files to the mail merge wizard individually. It is conditional based on the letter code field, but the initial condition document/coding is invisible from the user end of things. From the setup point of view, it really looks like we are just adding a file for each condition.

GrahamSkan

So the merge merge wizard is not the one in word that sets up the mail merge document and, perhaps, runs the merge.

It sounds as if, from the Word point-of-view, the database is running several separate mail merges.

rporter45

ASKER

Correct, but it must have a background conditional process as the merged letters all come back into one final merged document.

GrahamSkan

Is the unexpected formatting always Calibri bold font, size 8? I can't actually reproduce the problem, but I notice that the field is in a cell that is part of a set of rows where the cells in the first column are all merged and have a font like that.

My guess is that it's a bug, Unfortunately, because I can't reproduce it, I can't try any workarounds .

rporter45

ASKER

I definitely took a look at the formatting of the column next to it as well. However, all 6 merge conditions have the exact same bottom portion and only one of the letters is doing this.

I think I am going to try and recreate the mail merge as a whole and see if it happens again. I have just been spinning my wheels trying to figure it out and maybe the solution really is that the mail merge is corrupt somewhere in the background.

Believe me, having a second opinion that it is a bug is more helpful than you know :)

Thank you so much for taking the time to help!

ASKER CERTIFIED SOLUTION

GrahamSkan

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial