Hi Dragan,

I may not have explained myself properly :

The problem is a bug in FoxPro 5.0a with SP3. Some of the memo fields
I am reporting on have extraneous spaces at the end of them, sometimes as much as 60 spaces, so I used the perfectly valid @T format code to have Visual
FoxPro trim the field before reporting on it. Using that method I hit
a bug in VFP whereby it reports "String is too long to fit (Error 1903)"
on fields that are longer than 254 characters, consistently. So I got rid of
the @T format code and reported instead on ALLTRIM(Memo_Field), which
does what I want anyway.

So my requirement is SOLVED, but, as you point out, the original problem
is not solved. For your information I have logged a bug report on the
Microsoft FoxPro website.

Regards,
Michel.

====================== Original message follows ====================

>>Long memo field problem SOLVED.
>>
>>If you use @T as your Format for the memo field, the Report Designer
>>outputs the "String too long to fit" error message. The work around
>>is to use ALLTRIM(Memo_Field) if you do not want to print extraneous
>>spaces.
>>
>Then it is not solved. Trimming made your memos just somewhat shorter, and in your case it was short enough. Just try to make your memo twice as long. Paste some text (not spaces) and see what happens when it goes over the 255 char limit.
>
>I'm also interested in a solution to this, and I'd put one here if I had it.