Vlad,

Thanks for the reply. Yes, I think this is my case. I just tried this idea, but it didn't work, so may be I'll abandon it now. On the other hand, your idea also doesn't work quite right (I'm sure, you know about it). The question is: is it possible at all without too many hassles?

BTW, I remember those days too :) At my work in Russia we used Matrix printers and I sent different escape codes. chr(12) also worked fine (remember my other thread of printing additional blank page, uf, I'm so glad I solved this problem).

Do you have other ideas?

Thanks in advance.

>Hi!
>
>Nadya, I remember in one of my thread I already discussed this thing. ESC codes for printer work only if your printer, printer driver and printer options match to the printing optimisation level when page printed using character by character string printing. Just simple switching on option of printer to print text as graphics prevents Marty's method from work. What say about font, printer, printer driver etc etc? I remember old nice days when all reports were printed on the matrix printer using just text and ESC codes. Now this is completely incorrect approach because it usually does not works and quite not flexible when moving to different printers and computers.
>
>>>Yep, it worked for me. I'm printing on an HP Laserjet 5i. The escape codes I used are labeled as laserjet codes in my reference, so this wouldn't be a portable solution. It would only work on a laserjet or compatible. I think if I were faced with your situation, I'd probably go the route Mike Helland recommended and use two columns. Sometimes I have to help my clients save themselves from themselves.
>>>
>>>Marty
>>
>>Marty,
>>
>>I created two Report variables StartBold and EndBold. Put your ESC expression chr(17)+the rest in initial and stored values.
>>Then I put StartBold+alltrim(buyer)+EndBold+address+stateuse in the field. May be this was the problem and I have to create one line expression, like you did?
>>Though, I'm not sure, do we use the same printer or not...
>>
>>I can not use Mike's suggestion (it would be the easiest thing), because we produced this report for years (it was designed in R&R) and can not just change its appearance.
>>
>>The other simple idea is to use Curier New, but again, my manager doesn't like its look.
>>
>>Therefore, I have to find another solution. Vlad's idea about TxtWidth works, but it doesn't always place comma on the correct spot (because TxtWidth is based on the average width of the letter).