Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.word.mailmerge.fields
|
|||
|
|||
Excel superscript not holding
User has Excel and Word 2002, SP-3
User is merging from an Excel database which has some items formatted as superscript, such asthe 2 in H2O. When merged into a Word document the superscript formatting is lost. We do have "Confirm Conversion at Open" checked and are using DDE to do the merge. Any ideas why the formatting from Excel is not holding? TIA! |
#2
Posted to microsoft.public.word.mailmerge.fields
|
|||
|
|||
Excel superscript not holding
Formatting (fonts, sizes etc.) are lost when you merge, regardless of the
connection type. In this case you may be able to get around it by a. cutting/pasting the sheet into a Word document (if there aren't too many columns) b. if the field in question is called xyz, instead of { MERGEFIELD xyz } use { REF xyz } or just { xyz } Longer term, it might be better to use the correct subscript in a Unicode font that contains all the necessary characters - in that case, if you connect using OLEDB and ensure that you use a suitable Unicdoe font in your Word document as well, the subscript should get through. Peter Jamieson "Brenda Rueter" wrote in message ... User has Excel and Word 2002, SP-3 User is merging from an Excel database which has some items formatted as superscript, such asthe 2 in H2O. When merged into a Word document the superscript formatting is lost. We do have "Confirm Conversion at Open" checked and are using DDE to do the merge. Any ideas why the formatting from Excel is not holding? TIA! |
#3
Posted to microsoft.public.word.mailmerge.fields
|
|||
|
|||
Excel superscript not holding
Hi Peter/Brenda,
A small addition to Peter's posting. Sub- and Superscripts are NOT brought across the mail merge interface, even when the data source is a Word table. The only way to include them, short of the Unicode solution Peter suggests, is to create them using EQ fields. Formatting (fonts, sizes etc.) are lost when you merge, regardless of the connection type. In this case you may be able to get around it by a. cutting/pasting the sheet into a Word document (if there aren't too many columns) b. if the field in question is called xyz, instead of { MERGEFIELD xyz } use { REF xyz } or just { xyz } Longer term, it might be better to use the correct subscript in a Unicode font that contains all the necessary characters - in that case, if you connect using OLEDB and ensure that you use a suitable Unicdoe font in your Word document as well, the subscript should get through. User has Excel and Word 2002, SP-3 User is merging from an Excel database which has some items formatted as superscript, such asthe 2 in H2O. When merged into a Word document the superscript formatting is lost. We do have "Confirm Conversion at Open" checked and are using DDE to do the merge. Any ideas why the formatting from Excel is not holding? Cindy Meister INTER-Solutions, Switzerland http://homepage.swissonline.ch/cindymeister (last update Jun 8 2004) http://www.word.mvps.org This reply is posted in the Newsgroup; please post any follow question or reply in the newsgroup and not by e-mail :-) |
Reply |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
Why isn't all my Excel data merging into my Word labels document? | Mailmerge | |||
Difficulty pasting Excel data into Word table only in XP versions | Tables | |||
Mail Merge Issue With Office 97 - Excel Data Source | Mailmerge | |||
Excel worksheet in Word linked text boxes | Page Layout | |||
Word Field Codes in Excel data file | Mailmerge |