View Single Post
  #6   Report Post  
Posted to microsoft.public.word.mailmerge.fields
Peter Jamieson
 
Posts: n/a
Default Data Trucated in word merge with excel source

Well, I've tried most of the things I could think of here and in essence,
the behaviour only changes when I mix text and numbers (or some other form
of non-text data) in the column where you want the long texts in the first
25 rows of the spreadsheet. Nothing else really makes it go wrong.

So I have to conclude that since you don't have such a mix, either I'm
missing something, or my test data isn't complex enough (it's fairly
simple), or there's some form of corruption problem on your machine,
orthere's something else going on (I think that probably covers it!). It's
difficult to know how to proceed. If the "copy the sheet into Word and use
that as the data source" approach works, there is at least /a/ way to do
your merge. If the problem were occurring here, I would certainly consider
trying the following things
a. making absolutely sure that the OLEDB provider was not treating some of
the cells in the column in question as numeric
b. experimenting with a very simple sheet with two columns to see if that
worked. If it did, I would try recreating my Excel sheet from scratch,
especially if it has been upgraded from an earlier version of Excel
c. recreating Word's normal template and/or data key (see
http://word.mvps.org/FAQs/AppErrors/...peningWord.htm )
d. inserting 25 rows at the top of my sheet, with long text data in the
appropriate column, and excluding the first 25 rows in the merge

Peter Jamieson


"BAW" wrote in message
...
Actually, all the data is text (actaully a description). Whenever the
description is very long, it will cut off the words. The shorter
descriptions merge properly. It looks like it is at about 255 characters,
but I am actaully assuming that is the case on each of the separate
"lines".
I appreciate you looking into this!!

"Peter Jamieson" wrote:

I have spoken with our IT person about changing
the registry. He did not recommend it


Fair enough. I doubt we'll ever discover why the machines are different.

I'm having another look at this as I got halfway through some experiments
last year, but it is certainly the case that mixing text and numeric
values
in a column can result in different behaviour depending on what is in the
mix and what settings are in force. It may take some time...

Meanwhile, can you check some things at your end. My current tests
suggest
that you probably have some cells in the "truncated" column that just
contain numbers or perhaps date/times. if so, can you make a copy of your
sheet and change the cells (perhaps using Edit|Replcae) that have
non-text
values into text values, and see if your longer texts then magically
reappear in the merge?

Peter Jamieson
"BAW" wrote in message
...
We are using Word 2003.. and I have spoken with our IT person about
changing
the registry. He did not recommend it and said that none of the other
machines should have been altered.. Back to square one!! I do have a
work
around by just splitting the cell, but would rather not if there is a
fix....

"BAW" wrote:

I have a word merge that pull data from an excel source into a table.
One of
the cells in excel has data over 255 characters long. All of the data
does
show up within excel, but when I perform the merge, the data is
trucated
at
255 characters within the word table. I have previously performed the
same
merge with the same data (on another computer) and all of the data
(over
255
characters) was transferred into the merge. Is there ANYTHING I can
do
to
ensure that all the data is transferred? I have previously posted a
similar
message, but at the time, thought the data was under 255 characters.
The
suggestion was to try using DDE- which didn't work, but when I got it
to
work
on another co-workers computer, I didn't pursue it further. Now as I
am
trying to re run the querry, it won't work on any of the computers in
the
office, so I am back to square one. By the way, the data is truncated
in
the
"select recipients" window... Thanks, in advance, for your help!