I am using a template to produce letters using embedded fields (eg {DOCPROPERTY BodyText *\ MERGEFORMAT }). The main letter has a font size of 12 and I would like to change it to 10 for the line at the bottom of the letter indicating to whom it is to be copied. Whatever I do the line prints out at size 12. I have cc {DOCPROPERTY CopyAddress } at size 10 in the template and I've tried using *\ CHARFORMAT as the optional switch. Is it possible to change the font? Thanks for any help.

If you replace \* MERGEFORMAT with \* CHARFORMAT the field result should reflect the font size (and other formatting) specified at the location of the field. (More specifically, it reflects the formatting applied to the first character of the field code.)

__________________
Stefan Blom
Microsoft Word MVP

Microsoft 365 apps for business
Windows 11 Professional

Thanks Stefan but I've done that and the line still prints at 12 despite the whole field being 10 in the template document. Are there any other options?

Can you share the document (remove any sensitive information first)? You can attach it to a message in this thread.

__________________
Stefan Blom
Microsoft Word MVP

Microsoft 365 apps for business
Windows 11 Professional

I've attached the template minus the header and footer. The letters are clinic letters that are generated from an Access database (private, not commercial). I've uploaded it as a Word document because I couldn't attach it as a .docm file. Thanks again for your help Stefan.

Attached Files

Clinic letter template.docx (19.9 KB, 10 views)

When I open the attached document I can tell that the last paragraph has Times New Roman size 10 points applied to it as direct formatting. If you change this, are you saying that the formatting comes back as you update the field?

__________________
Stefan Blom
Microsoft Word MVP

Microsoft 365 apps for business
Windows 11 Professional

Yes. The whole letter, including the last line prints as size 12

I suspect the problem is with the data source, then. If it adds Rich Text fields, that might explain what goes wrong. I know too little about these sort of things.

Hopefully, macropod (Paul Edstein) will be able to help.

__________________
Stefan Blom
Microsoft Word MVP

Microsoft 365 apps for business
Windows 11 Professional

Happy New Year. Sorry to contact you again after so long, but I haven't managed to solve my problem. You mentioned macropod. How do I contact him?

Thanks again for your help.

Paul is an Administrator in this forum, so he should be able to notice your post. Or you could always post a new thread, adding what you have tried (unsuccessfully) so far.

__________________
Stefan Blom
Microsoft Word MVP

Microsoft 365 apps for business
Windows 11 Professional