Reply
 
Thread Tools Display Modes
  #1   Report Post  
Posted to microsoft.public.word.mailmerge.fields
Brenda Rueter
 
Posts: n/a
Default 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   Report Post  
Posted to microsoft.public.word.mailmerge.fields
Peter Jamieson
 
Posts: n/a
Default 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   Report Post  
Posted to microsoft.public.word.mailmerge.fields
Cindy M -WordMVP-
 
Posts: n/a
Default 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

Posting Rules

Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Why isn't all my Excel data merging into my Word labels document? Cindy Meister Mailmerge 0 August 6th 05 09:19 AM
Difficulty pasting Excel data into Word table only in XP versions Digitonomy Tables 0 February 28th 05 12:33 AM
Mail Merge Issue With Office 97 - Excel Data Source Matt Thorley Mailmerge 1 February 15th 05 11:38 PM
Excel worksheet in Word linked text boxes Eduardo Oliveira Page Layout 0 January 5th 05 11:23 PM
Word Field Codes in Excel data file mranz Mailmerge 7 December 11th 04 09:02 AM


All times are GMT +1. The time now is 08:31 PM.

Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Microsoft Office Word Forum - WordBanter.
The comments are property of their posters.
 

About Us

"It's about Microsoft Word"