More Mail Merge truncating

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

cheshirecat - 22 Aug 2006 20:14 GMT

I've been reading the threads and trying the advice to no avail. When I merge
into Word 2003 from an Excel spreadsheet that's pulling data off a SQL
Server, two fields are truncated at 255, but a third is not. I've tried
padding the first row, but it doesn't work, nor does chosing the connection
method. Any ideas?

thanks,
Linda

Reply to this Message

Doug Robbins - Word MVP - 22 Aug 2006 20:51 GMT

Have you confirmed that the data is complete in the Excel spreadsheet?
Maybe the truncation is between the SQL Server and Excel.

Signature

Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP

> I've been reading the threads and trying the advice to no avail. When I
> merge
[quoted text clipped - 6 lines]
> thanks,
> Linda

Reply to this Message

cheshirecat - 22 Aug 2006 20:57 GMT

Yes, I have. The data is complete in Excel.

> Have you confirmed that the data is complete in the Excel spreadsheet?
> Maybe the truncation is between the SQL Server and Excel.
[quoted text clipped - 9 lines]
> > thanks,
> > Linda

Reply to this Message

Doug Robbins - Word MVP - 22 Aug 2006 21:00 GMT

Then you need to look at the difference between the data for the one field
that merges correctly and those that don't.

Signature

Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP

> Yes, I have. The data is complete in Excel.
>
[quoted text clipped - 11 lines]
>> > thanks,
>> > Linda

Reply to this Message

cheshirecat - 22 Aug 2006 21:51 GMT

where would I look? in Excel? In Word? In SQL? Does it matter how the field
types are defined in SQL? I've copied data from the incorrectly merging
fields into Word and Notepad to compare them against what's working and the
only noticible difference in the non-truncating fields is that they start and
end with angle brackets (because it's XML strings).

> Then you need to look at the difference between the data for the one field
> that merges correctly and those that don't.
[quoted text clipped - 14 lines]
> >> > thanks,
> >> > Linda

Reply to this Message

Peter Jamieson - 22 Aug 2006 21:57 GMT

The trouble with "the advice" is that none of the methods of connecting to
Excel data (or any other kind of data) can be guaranteed to do what you
need: each has its own limitations, and there are quite a few.

In this case, are you in a position to connect directly to the SQL Server?
If so, that still may not solve the problem, but it may well cut out the
"middle man".

Peter Jamieson

> I've been reading the threads and trying the advice to no avail. When I
> merge
[quoted text clipped - 6 lines]
> thanks,
> Linda

Reply to this Message

cheshirecat - 24 Aug 2006 20:59 GMT

I didn't want to go that route since I don't know SQL, but found a colleague
who does and we think this will work just fine. Thanks to everyone!

> The trouble with "the advice" is that none of the methods of connecting to
> Excel data (or any other kind of data) can be guaranteed to do what you
[quoted text clipped - 15 lines]
> > thanks,
> > Linda

Reply to this Message