Could it be the case described below?

Hyperion Systems wrote in message news:<8mbu0v$lv0@flatland.dimensional.com>...
I was getting an error in the report writer. 'String too long to fit'
on a memo field which was about 400 characters long. Strange. I even
had another memo field which was longer and did not generate the
error. Quickly looking to see what the difference between the two was,
I found that one had the @T format to left justify it, the one that
worked did not. So I removed the formatting since it left justifies
anyway, and it worked. So I checked the knowledge base and found a
similar error was generated when trying to use the upper case
formatting in the report writer. Seems the report writer has problems
formatting strings longer than 254 characters, a problem obviously
carried forward when they ported the report writer from 2.6, instead
of redesigning it. Just wanted to warn everyone to beware this
problem.

Oh, and the knowledge base says this behavior is by design. In the
case of wanting to upper case the memo string, use UPPER() in the
field box, and not the upper case format option.

- John


>Cathy
>
>Forgive me for switching to another issue on the same report, but you seem to be widely regarded as the Ace on reports!!!!
>
>I am now getting the message "string too long to fit" when printing alltrim(memo) with stretch. Is there a limit to the memo field size I can print?
>
>Thanks
>
>Colin