Thank you Ulrich Is there an other way of sendig these special codes to te printer? Putting them in a label doesn't work either. Thanks Anne

Hi anne, what do you see in your output file? Perhaps this code is sorrounded by some additional code so it is not converted any more. what about using a dummy Unifield (which is unhidden if $printing) as another way to persuade uniface to pass the data unmodified? Last chance would be to amend the Device Translation Table you use: add your characters to the "^INIT" macro. Another option would be a logical printer where the physical printer has set duplex printing ON. But using logical printers are a real pain to manage in production environments, as I have heard. Not quite sure if the new uniface versions offer a chance to manipulate standard printer settings.

Hi anne, and a very unfair way (not quite sure how long this will work) using brutal force: export the form and manipulate the formpic of the XML file directly: have a look how the "old" exports hold the PCL sequence and just paste it to the new form. As I mentioned earlier: if you do not open the component and modify it, "old" component-text is still processed properly.

Thank you very much Ulrich. I had tried the translation table but no succes either The solution of defining the logical printer is no option in this company. I trie the unifield solution. Keep you informed. Best regards Anne

Hi Anne, there is no "form text" any more. If you open a form or report, existing form texts are converted to labels. I have seen customers where opening a report is not allowed because of this automatism, as I was told, the converted ones cause a different layout of the generated reports. For the PCL code: try a ; instead of the ^027 for the esc