>>The @SAY and ?? printing works in VFP. It's a great feature when thousands of documents, like invoices or packing slips, need to be printed in a batch. I have many installs that rely on the @SAY feature.
>>
>>There is the "???" inline control code function.
>>
>>There must be some kind of "slew" escape sequence codes that would allow you to use "???" to send the command. Sometimes, on some types of printers, and I don't know why, a blank (" ") is needed before or after the ??? code is sent.
>>
>>What kind of printer is it?
>>
>It's oki dotmatrix ub printer. We may want to print lots of forms at once. We have already defined report that works in DOS. Are you saying we may want to replicate its output with ??? or SAY commands?

If you don't have the original DOS reports, you may just (backup the converted reports first and)

USE the.frx
replace all vpos with vpos*1.05

If you do have the originals (they may still be on the disk, under a slightly different extension), you may want to fiddle with the transprt.prg and rebuild convert.app (all in xSource.zip). It calculates the vpos (in 10000ths of inch) from the old vpos (in characters). The procedure where it does that is
CVTREPORTVERTICAL(), and you actually need to adjust the g_rptlinesize, which is then calculated from the fontmetric() of the font you selected for conversion.
If you look for g_rptlinesize, you'll find where it sets Courier New, 10, N as default font for the reports. You may choose another font, fontsize etc, rebuild the convert.app and give it another try, or you may want to fiddle deeper with the way it calculates the vPos.