>I tried your suggestion. It didn't work for me. I am working with VFP 3.0 if that makes any difference. Do you have any other ideas?
>
>Joe
>

>>
>>Func GoDuplex
>>?? CHR(27) + "&l1S" && duplex code
>>return ""
>>

(This goes for Tim, too).
You can still include a report form field with CHR(27) + "&l1S" as value, but I'm not sure how will it behave, depending on its position. Well, the functions like this worked under DOS :), and the reason why we did it this way is that in FPD, when you issued some escape sequences in a report (and we did it all the time), they got printed fine, but the report runtime took their length into account, and all the objects to the end of the line were moved left for the length of the escape string.

Now in bitmapped environment it may be actually working different - any object should be printed with escape sequences which will define its position on paper, regardless of the actual width of objects to the left of it on the same line. I'm currently on a vacation (i.e. using my home machine :), so I can't try it out right on until Monday. My printers don't have duplex mode, though, but I'll try to code some bold or italics.