Thanks, Mark.

In another test report this works fine. In the actual report I got some weird results. Perhaps I did something wrong. I'll download it at home one more time and try again.

Thanks.

>Hello Nadya
>
>Its getting late here so I may be misunderstanding, but if Vlad's solution is almost right but for the commas, perhaps adding the commas earlier would help.
>
>Example below
>
>

space(_screen.TextWidth(alltrim(buyer)+", ")/_screen.TextWidth(" "))+Address

+ etc.
>
>
>hope this helps
>
>Mark
>>
>
>
>>I'm trying your idea now. I got very weird results.
>>I put two fields: one alltrim(Buyer) in Times New Roman, Bold, 8
>>Another

space(_screen.TextWidth(alltrim(buyer))/_screen.TextWidth(" "))+", "+Address

+ etc. Only first record shows Address part. Other records don't show Address at all. Perhaps, we can not use _screen object in a Report. May be I have to do through UDF.
>>
>>>PMFJI,
>>>
>>>Hey Nadya,
>>>
>>> Another angle you could take on Vlad's original suggestion is to use _SCREEN.TextWidth() instead of the command TXTWIDTH(). You'd need to set the the _SCREEN fontname/size to the same as your report form. If that's not acceptable, you could create a non-visible form object (forms have textwidth() too) and just call its method.
>>>
>>>The difference between _SCREEN.TextWidth() and TXTWIDTH is that the former returns the actual width in pixels, not the average. Using the actual width would prevent the trouble you're having with the comma not lining up.
>>>
>>>HTH,
>>>
>>>Marty