Skip to main content
Skip table of contents

POPO - ESCAPES

Initializing the Printer
When problems are encountered printing purchase orders, often times the printer assigned to print POs needs to be initialized. A common code can be created to initialize the printer each time POs are to be printed. The following describes the common code used to initialize a Rugged Writer.
Code Category: POPO
Code Value: ESCAPES
Short Description: If PAGE is entered, the system will not print the ending lines (blanks) of the last page of the Purchase Order.
Medium Description: Used to describe the common code.
Long Description: Enter the escape sequence to be used when initializing the printer on which Purchase Orders will be printed. When entering the Escape character, use the ^ symbol. As an example, the escape sequence that may be necessary when using Rugged Writer printers is "&l0L"; that is "" (Shift "6") & (Shift "7") "l" (Lower case "L") "0" (Numeric zero) and "L" (Upper case "L"). Additionally, "\nnn" (where nnn is a three-digit decimal number) to include any ASCII character in the starting and ending escape sequences. For example, \065 would print an "A."
Associated Numeric Values
1: Enter the number of Continuation Statements to print (system default is 3).
2: Enter the column number where the Continuation Statement should start printing (system default is 30).
3-5: Reserved for future use.
Associated Codes
1: Enter the number of lines per Purchase Order (system default is 66).
2: Leave blank to work as usual. Optional to enter NOEXTRAPAGE to cause the system to remove extra lines that appear before the starting escape sequence.
3-5: Reserved for future use.
Associated Descriptions
1: Enter the Continuation Statement to print.
2: Enter the closing escape sequence for the printer, or \nnn (where nnn is a three-digit decimal number) to include any ASCII character in the starting and ending escape sequences. For example, \065 would print an "A."
3-5: Reserved for future use.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.