255 character limit on merge fields?

[Dunc]

I am trying to make a catalog by merging fields from an Excel database into
a Publisher "catalog".

I get a warning that some of my fields exceed 255 characters and that those
in excess will be cut off.

Is there a way for me to get around this? I am not really anxious to split
many of the text pieces into 255 character pieces.

I will have around 350 records to deal with.

Would it make a difference if I merged from a Access database?

Thanks

Dunc

 

[Dunc]

I forgot to mention I am using Publisher 2003.
Would 2007 make a difference?

 

[Mary Sauer]

It is the same in 2007...

Merged fields are truncated to 255 characters in a Publisher 2007 or Publisher
2003 publication
http://support.microsoft.com/kb/829172/en-us

 

[Dunc]

Well Thanks Mary... (I guess ;-) )

I sure wish you had better news.

I guess I am into making multiple description fields....

And thanks for the link to the support article...

That was nice of you to include that!

Dunc

 

[Delahaye]

It is the same in 2007...

Merged fields are truncated to 255 characters in a Publisher 2007 or Publisher
2003 publication
http://support.microsoft.com/kb/829172/en-us

--
Mary Sauer MSFT MVP
http://office.microsoft.com/
http://msauer.mvps.org/
news://msnews.microsoft.com

"Dunc" <(e-mail address removed)> wrote in message
news:(e-mail address removed)...
>I forgot to mention I am using Publisher 2003.
> Would 2007 make a difference?
> "Dunc" <(e-mail address removed)> wrote in message
> news:(e-mail address removed)...
>>I am trying to make a catalog by merging fields from an Excel database into a
>>Publisher "catalog".
>>
>> I get a warning that some of my fields exceed 255 characters and that those
>> in excess will be cut off.
>>
>> Is there a way for me to get around this? I am not really anxious to split
>> many of the text pieces into 255 character pieces.
>>
>> I will have around 350 records to deal with.
>>
>> Would it make a difference if I merged from a Access database?
>>
>> Thanks
>>
>> Dunc
>>
>
>

Hi
is there the same problem with 2013 and 2016 ?
Thanks