Mail Merge truncates memo fields

[Jeremy]

I have SP-3 and I have followed all the instructions in
Article - 242072, but I still have problems with memo
fields being truncated in word merge. Please help. I am
using Office 2K. Thanks.

jmcqueen@NO beau SP rivage AM .com

 

[Cindy M -WordMVP-]

Hi Jeremy,

I have SP-3 and I have followed all the instructions in
Article - 242072, but I still have problems with memo
fields being truncated in word merge. Please help. I am
using Office 2K.

How many characters are coming through?

What's the data source?

Have you sorted the data so that a record with > 255
characters in the memo field is the first record?

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update
Sep 30 2003)
http://www.mvps.org/word

This reply is posted in the Newsgroup; please post any
follow question or reply in the newsgroup and not by e-mail

 

[jcr50]

I've had this issue before and banged my head on the wall for
awhile...first question...is your datasource for your mailmerge
document an actual talbe, or a query based on a table(s)?

It's been awhile since I had this problem but hope this helps...

I think I used an Access query as the datasource, and the memo field
seemed to come through to the query no problem, but if more than 255,
it would end up truncated or as question marks on the mailmerge
document.

The way I found around this was to set up a temp table and insert the
record from the query into the temp table. Then use the temp table as
the datasource for the document instead of the query.

Hope this helps

JCR50

 

[Jeremy]

Thanks, but my data source is a table. I split the memo
field into two text fields, but what happens is when the
field is split at a point where there is a space, Word
(not Access) truncates that space. The result is "mustbe"
instead of "must be". Thanks.

 

[Cindy M -WordMVP-]

Hi Jeremy,

Thanks, but my data source is a table. I split the memo
field into two text fields, but what happens is when the
field is split at a point where there is a space, Word
(not Access) truncates that space. The result is "mustbe"
instead of "must be". Thanks.

I've been hoping a light-bulb would go off, somewhere, but so
far not much luck <sigh>

Only two other possible ways around this occur to me:

1) Try a different connection method

2) Try exporting to a file in RTF format (comma-delimited, or
similar)

For the former, activate the "Select method" checkbox in the
Word Open Datasource dialog box. If you're not doing this
already, it means DDE is the current connection method. In
that case, try ODBC instead.

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Sep
30 2003)
http://www.mvps.org/word

This reply is posted in the Newsgroup; please post any follow
question or reply in the newsgroup and not by e-mail