KeystoneIntranet - User contributions [en]

Training Outline: Ticket Printing

2026-02-10T17:49:42Z

Mbarker:

= Training Outline - Dispatch System =

== Keystone Options ==

=== COD Payment Information ===

Allowing Dispatch to enter Payment Information:

'''Per Order:'''
This option enables "Cash Payment Entry" program under the Dispatch menu.
#Accounts Receivable --> COD Prepay Support

'''Per Ticket:'''
These options will present the "Payment Information" popup when a ticket is created.
'''This will prompt for ALL priced tickets/orders.'''
#Dispatch --> Ticket Printing Options --> Ask Payment Information
#Dispatch --> Ticket Maintenance/List Options --> Ask Payment Information

= Training Outline - Ticketing System =

== CONFIGURING Keystone OPTIONS ==

=== Create Ticket Layout ===

=== Pricing Options ===

#Allow Price/Disc Changes
#Show Prices On Screen For Non Cods
#Print Prices On Tickets
##Cods Only
##Always
##Never
##Cods - Ask All Others
#Pricing Control (Remote Only)
##Ticketing System
##Office
=== File Maintenance Options On Ticketing Menu ===

#Product
#Customer
#Price
#Job Price
=== Ticket Printing Program Options ===

#Show A/R Balance & Total Open Slips
#Ask For Truck, Time, Miles
#Ask Next Delivery Time
#Ask For Payment
=== Remote Transfer Options ===

#Print Report
#Drive To Be Used

AP Check Form Fields

2026-01-29T15:24:06Z

Mbarker:

(Created 12/14/2022)

===A/P Check Form Database Fields===

<pre>
CHECK_AMOUNT
H.CHECK_MEMO
H.NAME
H.ADDRESS_1
H.ADDRESS_2
H.CITY
H.STATE
H.ZIP
H.SESSION_NO CM_SESSION_NO
H.TRANS_NO CM_TRANS_NO
D.INVOICE_NO
D.INVOICE_DATE
D.DUE_DATE
D.DISCOUNT_DATE
D.RETAINAGE_DATE
D.GROSS_AMOUNT
D.PAID_AMOUNT
D.RETAINAGE_AMOUNT
D.PAID_THIS_CHECK
D.DISC_THIS_CHECK
D.DISC_TAKEN
D.DESCRIPTION
D.PO_NUMBER
V.PARENT_VEND_ID
V.CREDIT_LIMIT
V.HIGH_CREDIT
V.VEND_CLASS
V.PAYMENT_TERMS
V.TEN99_CLASS
V.SECURITY_CLASS
V.LAST_PURCHASE_DATE
V.LAST_PAY_DATE
V.LAST_CHECK_NO
V.LAST_BANK_NO
V.CREDIT_LIMIT
V.PHONE_NO
V.FAX_NO
V.PAGER_NO
V.MOBILE_NO
V.EMAIL
V.URL
V.START_DATE
V.LAST_CONTACT_DATE
V.MTD_PURCHASES
V.YTD_PURCHASES
V.LAST_YEAR_PURCHASES
V.MTD_PAYMENTS
V.YTD_PAYMENTS
V.LAST_YEAR_PAYMENTS
V.MTD_DISC_TAKEN
V.YTD_DISC_TAKEN
V.FIN_CHARGE_CODE
V.TAX_CODE
V.COD_FLAG
V.TEMP_FLAG
V.TEN99_FLAG
V.AUTO_DIST_FLAG
V.USER_1
V.USER_2
V.TAX_AUTHORITY
C.NAME CONTACT
V.SEQUENCE_CODE
V.NOTES_1
V.NOTES_2
V.NOTES_3
V.NOTES_4
V.AP_GL
V.CASH_GL
V.DISC_GL
V.EXPENSE_GL
V.TAX_ID
V.CASH_BANK_NO
V.NAME_2
V.VEND_ID
</pre>

'''Written Check Amount Line:'''
<pre>
LINE +1 COLUMN 10 LEFT 80 FORMAT WRITTENND FIELD CHECK_AMOUNT
</pre>

====Notes:====
*H: Check Header
*D: Check Detail (invoice)
*V: Vendor
*C: Contact

===A/P Check Form Calculated Fields===

<pre>
CALC_WRITTENAMT
CALC_GROSSTOTAL
CALC_DISCTOTAL
CALC_VENDADDR1
CALC_VENDADDR2
CALC_VENDADDR3
CALC_VENDADDR4
CHECK_NO
COND_INVOICEDESC
</pre>

Keystone Forms

2026-01-29T13:59:30Z

Mbarker:

[[CATEGORY: FORMS]]

While forms can be stored in the customer directory (e.g. ...\cust\forms), this should only be done if the form is specific to a computer. Custom Forms belong in the database.

==Sections==
===Form Section===

{| border="3" cellspacing="0" cellpadding="3"
! Command
! Purpose
! Comment
! Keystone Version
|-
| BEGINCOPY n
| apply block of form only for nth copy
| applies to all form sections
| 2.7.16
|-
| CHAIN name
| the next form in the chain
|
|
|-
| COLUMNS n
| number of columns on each form
| used for labels
|
|-
| COPIES n
| number of copies of each form
|
|
|-
| CPI n
| characters per inch
|
|
|-
| ENDCOPY
| indicates end of COPY block
|
| 2.7.16
|-
| FONTNAME name
| default font for the form
|
|
|-
| LENGTH n
| number of lines on the form
| impacts automatic page breaks
|
|-
| LINES n
| number of lines for each label
| used for labels
|
|-
| LPI n
| Lines Per Inch - Vertical spacing between lines
| This will also change box sizing. Default: LPI 6
|
|-
| MARGIN top,left,bottom,right
| specify page margins
| default is no margins
| 3.6.18.1
|-
| OPTION EXTEND_DETAIL
| allow form detail to extend into footer area
|
| 2.1.4
|-
| OPTION IMAGE_FIX
| fix image drawing issue
| some printers print border on right/bottom edge of images
| 3.2.3.1
|-
| OPTION LANDSCAPE
| force landscape orientation for the form
|
| 2.6
|-
| OPTION SUMMARIZE_PRODUCTS
| summarize product totals when printing invoices
|
| 1.6.6
|-
| PDFPAGES n <nowiki>|</nowiki> ALL
| number of PDF document pages to include on form
| default is first page only
| 4.3.9.10
|-
| PRINTER name
| creates a virtual printer name
| Keystone can map this name to a physical printer with different settings per user
|
|-
| TITLE name
| descriptive name of this form
| some options display this to the user when selecting forms
|
|-
| VERSION n
| indicates the version number of the form
| used for special processing by some Keystone options
| 2.5.25
|-
| WIDTH n
| number of columns on the form
| increase as needed but keep in mind this will reduce the font size
|
|}

===Heading===
Information that prints 1 time at the top of the form.

Alternate headings (e.g. "HEADING 4") are used in certain types of forms for special sections of a form.

===Detail===
Information that repeats for each line of detail.

Certain forms may have alternate detail lines with unique behavior. This could be an alternate type of detail or sub-detail. e.g. "DETAIL 2" on an invoice is used to print comments.

===Total===
Information that prints at the bottom of the form.

{| border="3" cellspacing="0" cellpadding="3"
! Command
! Purpose
! Comment
! Keystone Version
|-
| NEWPAGE
| Start new page on a form
| Only verified for Total Section
| 3.3.1
|}

Sample Total with a NEWPAGE:
<PRE>
TOTAL

LINE 42

COLUMN 41
BOX 5,24,0,20
BOX 5,24
BOX 5,36
LINE +1 COLUMN 44 TEXT SUB TOTAL
COLUMN 65 FORMAT ######.00 FIELD CALC_SUBTOTAL

LINE +1 COLUMN 44 TEXT SALES TAX-
COLUMN 54 FIELD TAX_AUTHORITY
COLUMN 65 FORMAT ######.00 FIELD CALC_SALESTAX

LINE +1 COLUMN 44 TEXT TICKET TOTAL
COLUMN 65 FORMAT ######.00 FIELD CALC_TICKETTOTAL
NEWPAGE

LINE +2 COLUMN 1
LINE +1 COLUMN 30 TEXT *** WARNING ***
LINE +1 COLUMN 10 TEXT Cement is not good for you and It doesn't taste very good.
LINE +1 COLUMN 10 TEXT Do not eat cement or stuff made from cement. Do not eat
LINE +1 COLUMN 10 TEXT Tide Pods either.
LINE +1 COLUMN 1 LEFT IMAGE 2
! DoNotEatCement.jpg
LINE +3 COLUMN 13 TEXT RECEIVED BY:
COLUMN 26 TEXT ________________________________________
LINE +2 COLUMN 1
</PRE>

==Working With Forms==

===Formats===
<PRE>
LINE +1 COLUMN 1 FORMAT mm/dd/yy FIELD TICKET_DATE
COLUMN 10 RIGHT 7 FIELD TICKET_NO
COLUMN 18 FORMAT ####0.00 FIELD QTY_SOLD
COLUMN 27 FIELD UNIT_OF_MEASURE
</PRE>

*'''Date:''' The date April 5, 2018 with a format of '''mm/dd/yy''' will print as '''04/05/18''', '''mm/dd/yyyy''' as '''4/05/2018'''
*'''Right/Left''' Slide text to the right or left of the designated space.
*'''Numbers with # and 0:''' '''#''' is a placeholder that prints if needed. '''0''' will always print a value. Example: 403.25 printed with a format of '''####0.00''' prints as " 403.25", with a format of '''00000.00''' as "00403.25"

===Comments===
Lines that begin with a ! are comments. They can be removed as needed.
<PRE>
! AVAILABLE CALCULATED FIELDS
! ===========================
</PRE>

===Images===

In form Maintenance, select '''Load''' on the Images tab. 
[[Image:Frm ld img.png]]
Load the image.

When Setting up the form, refer to the image by number. The following code places an image in column 3, scaled to be 12 characters wide:
<PRE>
LINE 2 COLUMN 3
LEFT 12 IMAGE 2
</PRE>

===Conditions===
Conditions can be used to change the printed form logic, based on a field or form conditional value (Example 1.) IFNOT can be used to check if a condition is NOT true - it will still use ENDIF to close (Example 2.)

When using "IF" with a field, the form will run the logic if the field is '''not''' null or zero (Example 3.)

You can nest "IF" statements with "ELSE" to do multiple condition checks (Example 4.) Insert the first "IF" condition, then use "ELSE" followed by another "IF" statement. Note: If "ELSE" is on the same line as "IF" it will give unintended results.

<PRE>
!EXAMPLE 1 -- Print "INTERNAL USE ONLY" if COND_INTERNAL is met.
IF COND_INTERNAL
COLUMN 8 TEXT INTERNAL USE ONLY
ENDIF

!EXAMPLE 2 -- Print FIELD QTY_SOLD only if the comment condition is not met.
IFNOT COND_COMMENT
COLUMN 43 FORMAT ####.00 FIELD QTY_SOLD
ENDIF

!EXAMPLE 3 -- Print UNIT_PRICE, if UNIT_PRICE is not null or zero.
IF UNIT_PRICE
COLUMN 16 FIELD UNIT_PRICE
ENDIF

!EXAMPLE 4 -- Print PRODUCT_COST if COND_INTERNAL is met, otherwise print UNIT_PCT_DISC if it is not null or zero. If COND_INTERNAL is not met and UNIT_PCT_DISC is null or zero, nothing will print.
! -- Note that only ONE "ENDIF" is used despite the use of TWO "IF" statements.
IF COND_INTERNAL
COLUMN 70 FORMAT ####.000 FIELD PRODUCT_COST
ELSE
IF UNIT_PCT_DISC
COLUMN 70 RIGHT 8 FIELD CALC_DISCOUNT
ENDIF
</PRE>

=== CHAIN command: Creating Multiple Forms ===
The Chain command allows multiple forms to print at one time. These forms can be identical or unique, and can print to multiple printers.

The Chain command is used in the FORM section.
Syntax: CHAIN [formname].FRM (e.g. CHAIN ARTCK.FRM)

In order to use multiple printers, make sure that the printer ALIAS is unique for each of the forms. Make sure to update the Plant to point to the correct form. Then in Ticket Printing/ Printer setup you can assign each alias to a printer.

When mixing a special form and a standard form, it is probably best to have the special form chain to the standard form. This prevents you from needing to create a new standard form and makes setting up the printers easier. The Printer setup develops the Alias list from the primary form for each plant. So if a special form with a unique alias is used as the primary form for a plant, then that Alias will appear on the list.

===Bar Codes===
Here is a section from a sample ticket form file that shows how to print barcodes on ticket forms.

NOTE that this should work in a similar way for dot-matrix (With EPSON emulation) and laser printers. However, for dot-matrix printers the only (currently) supported bar code format is Code 39. For laser/inkjet printers you must have a bar code font available on the printer, and you would specify that font name where you see “FONTNAME BARCODE39” in the sample below.

<PRE>
FORM
LENGTH 66 WIDTH 80 PRINTER ARTicket
FONTNAME VERDANA

HEADING
LINE 1 COLUMN 1
FONTNAME BARCODE39
FORMAT 00000000 FIELD TICKET_NO
FONTNAME DEFAULT

LINE 8 COLUMN 5 FIELD PLANT_NO
COLUMN 10 FORMAT #0":"00 FIELD TICKET_TIME
COLUMN 30 FIELD TRUCK_NO
COLUMN 38 FIELD DRIVER_NAME
COLUMN 58 FORMAT MM/DD/YY FIELD TICKET_DATE
COLUMN 71
</PRE>

===Boxes/Shading===

The BOX command may be used in any form printing section (Heading, Detail, Total.) The syntax is as follows:

<code>
BOX Height, Width [,Weight [,Shading [,Color]]]
</code>

Example:
<pre>BOX 1,76,0,20,clYellow</pre>

Height and Width are expressed in printed characters.

Weight is optional (default is 8 pixels) and indicates the number of pixels for the box border. The border is drawn in the current COLOR setting (black is default.)

Shading is optional (default is no shading) and specifies the shading percentage (0-100.) Lower shading is brighter color, higher shading is darker color.

(Keystone 3.6.4.7+) Color is optional (default is black) and specifies the shading color. The borders are drawn in the current font color.

When Color is black it is treated as white internally, meaning that a lower shading will tend toward white (no shading) while a higher shading will tend toward black.

==See Also==
:[[Keystone Form Colors]]
:[[Sample Forms]]
:[[Payroll: Form Versions]]
:[[Invoice Form Fields]]
:[[Ticket Form Fields]]
:[[AP Check Form Fields]]
:[[Quote Form Fields]]

Keystone Forms

2026-01-29T13:57:53Z

Mbarker:

[[CATEGORY: FORMS]]

While forms can be stored in the customer directory (e.g. ...\cust\forms), this should only be done if the form is specific to a computer. Custom Forms belong in the database.

==Sections==
===Form Section===

{| border="3" cellspacing="0" cellpadding="3"
! Command
! Purpose
! Comment
! Keystone Version
|-
| BEGINCOPY n
| apply block of form only for nth copy
| applies to all form sections
| 2.7.16
|-
| CHAIN name
| the next form in the chain
|
|
|-
| COLUMNS n
| number of columns on each form
| used for labels
|
|-
| COPIES n
| number of copies of each form
|
|
|-
| CPI n
| characters per inch
|
|
|-
| ENDCOPY
| indicates end of COPY block
|
| 2.7.16
|-
| FONTNAME name
| default font for the form
|
|
|-
| LENGTH n
| number of lines on the form
| impacts automatic page breaks
|
|-
| LINES n
| number of lines for each label
| used for labels
|
|-
| LPI n
| Lines Per Inch - Vertical spacing between lines
| This will also change box sizing. Default: LPI 6
|
|-
| MARGIN top,left,bottom,right
| specify page margins
| default is no margins
| 3.6.18.1
|-
| OPTION EXTEND_DETAIL
| allow form detail to extend into footer area
|
| 2.1.4
|-
| OPTION IMAGE_FIX
| fix image drawing issue
| some printers print border on right/bottom edge of images
| 3.2.3.1
|-
| OPTION LANDSCAPE
| force landscape orientation for the form
|
| 2.6
|-
| OPTION SUMMARIZE_PRODUCTS
| summarize product totals when printing invoices
|
| 1.6.6
|-
| PDFPAGES n <nowiki>|</nowiki> ALL
| number of PDF document pages to include on form
| default is first page only
| 4.3.9.10
|-
| PRINTER name
| creates a virtual printer name
| Keystone can map this name to a physical printer with different settings per user
|
|-
| TITLE name
| descriptive name of this form
| some options display this to the user when selecting forms
|
|-
| VERSION n
| indicates the version number of the form
| used for special processing by some Keystone options
| 2.5.25
|-
| WIDTH n
| number of columns on the form
| increase as needed but keep in mind this will reduce the font size
|
|}

===Heading===
Information that prints 1 time at the top of the form.

Alternate headings (e.g. "HEADING 4") are used in certain types of forms for special sections of a form.

===Detail===
Information that repeats for each line of detail.

Certain forms may have alternate detail lines with unique behavior. This could be an alternate type of detail or sub-detail. e.g. "DETAIL 2" on an invoice is used to print comments.

===Total===
Information that prints at the bottom of the form.

{| border="3" cellspacing="0" cellpadding="3"
! Command
! Purpose
! Comment
! Keystone Version
|-
| NEWPAGE
| Start new page on a form
| Only verified for Total Section
| 3.3.1
|}

Sample Total with a NEWPAGE:
<PRE>
TOTAL

LINE 42

COLUMN 41
BOX 5,24,0,20
BOX 5,24
BOX 5,36
LINE +1 COLUMN 44 TEXT SUB TOTAL
COLUMN 65 FORMAT ######.00 FIELD CALC_SUBTOTAL

LINE +1 COLUMN 44 TEXT SALES TAX-
COLUMN 54 FIELD TAX_AUTHORITY
COLUMN 65 FORMAT ######.00 FIELD CALC_SALESTAX

LINE +1 COLUMN 44 TEXT TICKET TOTAL
COLUMN 65 FORMAT ######.00 FIELD CALC_TICKETTOTAL
NEWPAGE

LINE +2 COLUMN 1
LINE +1 COLUMN 30 TEXT *** WARNING ***
LINE +1 COLUMN 10 TEXT Cement is not good for you and It doesn't taste very good.
LINE +1 COLUMN 10 TEXT Do not eat cement or stuff made from cement. Do not eat
LINE +1 COLUMN 10 TEXT Tide Pods either.
LINE +1 COLUMN 1 LEFT IMAGE 2
! DoNotEatCement.jpg
LINE +3 COLUMN 13 TEXT RECEIVED BY:
COLUMN 26 TEXT ________________________________________
LINE +2 COLUMN 1
</PRE>

==Working With Forms==

===Formats===
<PRE>
LINE +1 COLUMN 1 FORMAT mm/dd/yy FIELD TICKET_DATE
COLUMN 10 RIGHT 7 FIELD TICKET_NO
COLUMN 18 FORMAT ####0.00 FIELD QTY_SOLD
COLUMN 27 FIELD UNIT_OF_MEASURE
</PRE>

*'''Date:''' The date April 5, 2018 with a format of '''mm/dd/yy''' will print as '''04/05/18''', '''mm/dd/yyyy''' as '''4/05/2018'''
*'''Right/Left''' Slide text to the right or left of the designated space.
*'''Numbers with # and 0:''' '''#''' is a placeholder that prints if needed. '''0''' will always print a value. Example: 403.25 printed with a format of '''####0.00''' prints as " 403.25", with a format of '''00000.00''' as "00403.25"

===Comments===
Lines that begin with a ! are comments. They can be removed as needed.
<PRE>
! AVAILABLE CALCULATED FIELDS
! ===========================
</PRE>

===Images===

In form Maintenance, select '''Load''' on the Images tab. 
[[Image:Frm ld img.png]]
Load the image.

When Setting up the form, refer to the image by number. The following code places an image in column 3, scaled to be 12 characters wide:
<PRE>
LINE 2 COLUMN 3
LEFT 12 IMAGE 2
</PRE>

===Conditions===
Conditions can be used to change the printed form logic, based on a field or form conditional value (Example 1.) IFNOT can be used to check if a condition is NOT true - it will still use ENDIF to close (Example 2.)

When using "IF" with a field, the form will run the logic if the field is '''not''' null or zero (Example 3.)

You can nest "IF" statements with "ELSE" to do multiple condition checks (Example 4.) Insert the first "IF" condition, then use "ELSE" followed by another "IF" statement. Note: If "ELSE" is on the same line as "IF" it will give unintended results.

<PRE>
!EXAMPLE 1 -- Print "INTERNAL USE ONLY" if COND_INTERNAL is met.
IF COND_INTERNAL
COLUMN 8 TEXT INTERNAL USE ONLY
ENDIF

!EXAMPLE 2
IFNOT COND_COMMENT
COLUMN 43 FORMAT ####.00 FIELD QTY_SOLD
ENDIF

!EXAMPLE 3 -- Print UNIT_PRICE, if UNIT_PRICE is not null or zero.
IF UNIT_PRICE
COLUMN 16 FIELD UNIT_PRICE
ENDIF

!EXAMPLE 4 -- Print PRODUCT_COST if COND_INTERNAL is met, otherwise print UNIT_PCT_DISC if it is not null or zero. If COND_INTERNAL is not met and UNIT_PCT_DISC is null or zero, nothing will print.
! -- Note that only ONE "ENDIF" is used despite the use of TWO "IF" statements.
IF COND_INTERNAL
COLUMN 70 FORMAT ####.000 FIELD PRODUCT_COST
ELSE
IF UNIT_PCT_DISC
COLUMN 70 RIGHT 8 FIELD CALC_DISCOUNT
ENDIF
</PRE>

=== CHAIN command: Creating Multiple Forms ===
The Chain command allows multiple forms to print at one time. These forms can be identical or unique, and can print to multiple printers.

The Chain command is used in the FORM section.
Syntax: CHAIN [formname].FRM (e.g. CHAIN ARTCK.FRM)

In order to use multiple printers, make sure that the printer ALIAS is unique for each of the forms. Make sure to update the Plant to point to the correct form. Then in Ticket Printing/ Printer setup you can assign each alias to a printer.

When mixing a special form and a standard form, it is probably best to have the special form chain to the standard form. This prevents you from needing to create a new standard form and makes setting up the printers easier. The Printer setup develops the Alias list from the primary form for each plant. So if a special form with a unique alias is used as the primary form for a plant, then that Alias will appear on the list.

===Bar Codes===
Here is a section from a sample ticket form file that shows how to print barcodes on ticket forms.

NOTE that this should work in a similar way for dot-matrix (With EPSON emulation) and laser printers. However, for dot-matrix printers the only (currently) supported bar code format is Code 39. For laser/inkjet printers you must have a bar code font available on the printer, and you would specify that font name where you see “FONTNAME BARCODE39” in the sample below.

<PRE>
FORM
LENGTH 66 WIDTH 80 PRINTER ARTicket
FONTNAME VERDANA

HEADING
LINE 1 COLUMN 1
FONTNAME BARCODE39
FORMAT 00000000 FIELD TICKET_NO
FONTNAME DEFAULT

LINE 8 COLUMN 5 FIELD PLANT_NO
COLUMN 10 FORMAT #0":"00 FIELD TICKET_TIME
COLUMN 30 FIELD TRUCK_NO
COLUMN 38 FIELD DRIVER_NAME
COLUMN 58 FORMAT MM/DD/YY FIELD TICKET_DATE
COLUMN 71
</PRE>

===Boxes/Shading===

The BOX command may be used in any form printing section (Heading, Detail, Total.) The syntax is as follows:

<code>
BOX Height, Width [,Weight [,Shading [,Color]]]
</code>

Example:
<pre>BOX 1,76,0,20,clYellow</pre>

Height and Width are expressed in printed characters.

Weight is optional (default is 8 pixels) and indicates the number of pixels for the box border. The border is drawn in the current COLOR setting (black is default.)

Shading is optional (default is no shading) and specifies the shading percentage (0-100.) Lower shading is brighter color, higher shading is darker color.

(Keystone 3.6.4.7+) Color is optional (default is black) and specifies the shading color. The borders are drawn in the current font color.

When Color is black it is treated as white internally, meaning that a lower shading will tend toward white (no shading) while a higher shading will tend toward black.

==See Also==
:[[Keystone Form Colors]]
:[[Sample Forms]]
:[[Payroll: Form Versions]]
:[[Invoice Form Fields]]
:[[Ticket Form Fields]]
:[[AP Check Form Fields]]
:[[Quote Form Fields]]

Invoice Form Fields

2026-01-09T17:51:51Z

Mbarker:

[[CATEGORY: FORMS]]
Fields available for the invoice form.

NOTE: In most cases just the field name is used. In some cases an alias is used and both the actual field name and the alias will be presented - in this case use the alias name on the form.

Examples:
<PRE>
IV.SESSION_NO INV_SESSION_NO,
IV.TRANS_NO INV_TRANS_NO,
SP.DESCRIPTION SALESPERSON_NAME,
</PRE>
Use:
<PRE>
INV_SESSION_NO
INV_TRANS_NO
SALESPERSON_NAME
</PRE>

A ticket Image can be added as:
<pre>
Add ticket form to invoice....
! ---------- Ticket Document Image
DETAIL 5
LINE 4 COLUMN 1 LEFT 80 IMAGEFIELD TICKET DOC_ID

</pre>

To add a Voided message for voided invoices:
<PRE>
IF CALC_VOIDFLAGMSG
LINE 32
FONTSIZE 48
COLOR clRed
BOLD ON
COLUMN 30 TEXT VOID
COLOR clBlack
FONTSIZE 8
ENDIF
</PRE>

To add a Barcode or Payment Link:
<PRE>
For QR Code:
LINE +1 COLUMN 15 LEFT 40 FORMAT BARCODE_QR FIELD CALC_LINK_PAYMENT_QR

For payment link:
COLUMN 15 LEFT 12 FORMAT PDF_HYPERLINK FIELD CALC_LINK_PAYMENT
</PRE>

==Invoice Form Fields==
<PRE>
IV.SESSION_NO INV_SESSION_NO,
IV.TRANS_NO INV_TRANS_NO,
IV.CUST_NO,
IV.INVOICE_NO,
IV.INVOICE_DATE,
SALES_TAX,
SALES_TAX_1,
SALES_TAX_2,
SALES_TAX_3,
IV.DEBIT_AMOUNT INVOICE_TOTAL,
IV.DISC_OFFERED DISC_AVAILABLE,
IV.DISC_VALID_DATE DISC_DATE,
NON_TAXABLE_1,
NON_TAXABLE_2,
NON_TAXABLE_3,
IV.PRIOR_AR_BALANCE,
IV.TAX_AUTHORITY,
IV.JOB_DESC,
IV.AGING_1,
IV.AGING_2,
IV.AGING_3,
IV.AGING_4,
IV.AGING_5,
IV.FINCHG_1,
IV.FINCHG_2,
IV.FINCHG_3,
IV.FINCHG_4,
IV.FINCHG_5,
IV.INVOICEMESSAGE_1,
IV.INVOICEMESSAGE_2,
IV.INVOICEMESSAGE_3,
IV.INVOICEMESSAGE_4,
IV.RETURNADDR_1,
IV.RETURNADDR_2,
IV.RETURNADDR_3,
IV.RETURNADDR_4,
IV.UMS_1,
IV.UMS_2,
IV.UMS_3,
IV.UMS_4,
IV.UMS_5,
IV.UMSTOTAL_1,
IV.UMSTOTAL_2,
IV.UMSTOTAL_3,
IV.UMSTOTAL_4,
IV.UMSTOTAL_5,
IV.CUST_NAME,
IV.CUST_ADDRESS_1,
IV.CUST_ADDRESS_2,
IV.CUST_CITY,
IV.CUST_STATE,
IV.CUST_ZIP,
IV.CREDIT_TERMS,
IV.DISCOUNT_MESSAGE,
(0) SPLIT_RATE, temporary
(0) SPLIT_LIMIT,
IV.PLANT_NAME,
IV.PLANT_SCREEN_ID,
IV.PLANT_ADDRESS_1,
IV.PLANT_ADDRESS_2,
IV.PLANT_PHONE_NO,
IV.SPACE_BETWEEN_TICKETS,
IV.NONTAX_TOTAL,
IV.TICKET_COMMENTS,
IV.PRODUCT_TOTALS,
IV.PRINT_CASH,
IV.PRINT_PRICED,
IV.PRINT_UNPRICED,
IV.CUST_COD_FLAG,
IV.CUST_USER_1,
IV.CUST_USER_2,
IV.DUE_DATE,
IV.VOID_FLAG,
IV.PLANT_NO INV_PLANT_NO,
IV.DIVISION_NO,
IV.CREDIT_AMOUNT,

// customer fields
CU.TAX_ID CUST_TAX_ID,

// sales header fields
SH.SESSION_NO TCK_SESSION_NO,
SH.TRANS_NO TCK_TRANS_NO,
SH.TICKET_NO,
SH.TICKET_DATE,
SH.SLUMP,
SH.MILES,
SH.TICKET_TIME,
SH.SALESPERSON,
SH.CUST_CLASS,
SH.SYS_LOC,
SH.PLANT_NO,
SH.JOB_PO_LOC,
SH.JOB_LOT,
SH.TRUCK_NO,
SH.TRAILER_1,
SH.TRAILER_2,
SH.SOURCE_FLAG,
SH.VOID_FLAG,
SH.PRICED_FLAG,
SH.OFFICE_PRICE_FLAG,
SH.ZONE,
SH.COD_FLAG,
SH.ELAPSED_TIME,
SH.BATCH_START_DT,
SH.BATCH_END_DT,
SH.LEAVE_PLANT_DT,
SH.ARRIVE_JOB_DT,
SH.BEGIN_POUR_DT,
SH.END_POUR_DT,
SH.LEAVE_JOB_DT,
SH.RETURN_PLANT_DT,
SH.CUSTOMER_PO,
SH.DRIVER,
SH.JOB_CLASS,
SH.PAYMENT_AMOUNT,
SH.CHECK_DATE,
SH.CHECK_NO,
SH.BANK_NO,
SH.SHIP_TO_1,
SH.SHIP_TO_2,
SH.SHIP_TO_3,
SH.SHIP_TO_4,
SH.DELV_INST_1,
SH.DELV_INST_2,
SH.DELV_INST_3,
SH.DELV_INST_4,
SH.ORDER_CODE,
SH.JOB_BLOCK,
SH.CUSTOM_1,
SH.CUSTOM_2,
SH.USAGE_TYPE,
SH.DOC_LINK,

// sales detail fields
SD.LINE_NO TCK_LINE_NO,
SD.COMMENT_FLAG,
SD.UNIT_PRICE,
SD.LIST_PRICE,
SD.UNIT_DISC,
SD.STD_DISC,
SD.QTY_SOLD,
SD.PRODUCT_CODE,
SD.UNIT_OF_MEASURE,
SD.DESCRIPTION,
SD.TAX_CODE,
SD.TAX_CODE_2,
SD.TAX_CODE_3,
SD.PRICE_SOURCE,
SD.GROSS_WEIGHT,
SD.TARE_WEIGHT,
SD.WEIGHT_UMS,
SD.SCALE_WEIGHT_FLAG,
SD.EXT_PRICE, .99.27

// salesperson fields
SP.DESCRIPTION SALESPERSON_NAME,

// product fields
PR.ROLLUP_FLAG,
PR.PRODUCT_TYPE,
PR.DESCRIPTION_1 PROD_DESCRIPTION_1,
PR.DESCRIPTION_2 PROD_DESCRIPTION_2,
PR.BASE_PRODUCT

// usage class fields
UC.DESCRIPTION USAGE_DESC, .32

// plant fields
PT.PLANT_NAME TCK_PLANT_NAME,
PT.PLANT_SCREEN_ID TCK_PLANT_SCREEN_ID,

// division fields
//DV.DIVISION_NO,
DV.DIVISION_NAME,

// tax authority fields
TA.DESCRIPTION TAX_AUTH_DESC
</PRE>

==Calculated Fields==
<PRE>
CALC_RETADDR1, CALC_RETADDR2, CALC_RETADDR3,
CALC_RETADDR4, CALC_INVOICEDATE, CALC_CUSTADDR1,
CALC_CUSTADDR2, CALC_CUSTADDR3, CALC_CUSTADDR4,
CALC_INVMSG1, CALC_INVMSG2, CALC_INVMSG3,
CALC_INVMSG4, CALC_CREDITTERMS, CALC_INVOICENO,
CALC_SUBTOTAL, CALC_NONTAXTOTAL, CALC_SALESTAX,
CALC_INVTOTAL, UNIT_PRICE, CALC_EXTPRICE,
CALC_TAXIND, CALC_TAXAUTH, CALC_DISCOUNTLINE,
CALC_DISCTOTAL, CALC_NFAGING1, CALC_NFAGING2,
CALC_NFAGING3, CALC_NFAGING4, CALC_NFAGING5,
CALC_NFAGING4&5, CALC_FINCHGBAL, CALC_AGING1,
CALC_AGING2, CALC_AGING3, CALC_AGING4,
CALC_AGING5, CALC_AGING4&5, CALC_DISCBALDUE,
COND_NONTAXTOTAL, CALC_UMS, CALC_UMSTOTAL,
COND_PRODUCTTOTALS, CALC_UMSTOTALLINE, JOB_PO_LOC,
CALC_DISCDATE, CALC_TAXRATEPCT, CALC_TAXINDYN,
CALC_MATLTOTAL, CALC_DELVTOTAL, QTY_SOLD,
CALC_TKROLL_MATLTOTAL, CALC_TKROLL_DELVTOTAL, CALC_TKROLL_TAXTOTAL,
CALC_TKROLL_TKTTOTAL, CALC_TAXABLETOTAL, ORDER_CODE,
TAX_RATE, SPLIT_RATE, SPLIT_LIMIT,
PLANT_NAME, PLANT_SCREEN_ID, PLANT_ADDRESS_1,
PLANT_ADDRESS_2, PLANT_PHONE_NO, CUST_USER_1,
CUST_USER_2, CALC_PAYMENTTOTAL, CALC_NETDUE,
CALC_PRIORARBAL, CALC_NEWARBAL, TICKET_JOB,
PS_DESCRIPTION, PS_QUANTITY, PS_U_OF_M,
PS_PRODUCT_CODE, PS_UNIT_PRICE, PS_EXT_PRICE,
CALC_VOIDFLAGMSG,
PS_TAX_IND,
TS_PLANT_NO, TS_TICKET_NO,
COND_TICKET_LINE_1,
COND_PRICE_ROLLUP,
COND_COD_CUST, COND_CASH_CUST,
TAX_DESC_1, TAX_DESC_2, TAX_DESC_3,
DOC_ID,
CALC_INVBAL
</PRE>

Keystone Forms

2025-07-14T18:10:25Z

Mbarker:

[[CATEGORY: FORMS]]

While forms can be stored in the customer directory (e.g. ...\cust\forms), this should only be done if the form is specific to a computer. Custom Forms belong in the database.

==Sections==
===Form Section===

{| border="3" cellspacing="0" cellpadding="3"
! Command
! Purpose
! Comment
! Keystone Version
|-
| BEGINCOPY n
| apply block of form only for nth copy
| applies to all form sections
| 2.7.16
|-
| CHAIN name
| the next form in the chain
|
|
|-
| COLUMNS n
| number of columns on each form
| used for labels
|
|-
| COPIES n
| number of copies of each form
|
|
|-
| CPI n
| characters per inch
|
|
|-
| ENDCOPY
| indicates end of COPY block
|
| 2.7.16
|-
| FONTNAME name
| default font for the form
|
|
|-
| LENGTH n
| number of lines on the form
| impacts automatic page breaks
|
|-
| LINES n
| number of lines for each label
| used for labels
|
|-
| LPI n
| Lines Per Inch - Vertical spacing between lines
| This will also change box sizing. Default: LPI 6
|
|-
| MARGIN top,left,bottom,right
| specify page margins
| default is no margins
| 3.6.18.1
|-
| OPTION EXTEND_DETAIL
| allow form detail to extend into footer area
|
| 2.1.4
|-
| OPTION IMAGE_FIX
| fix image drawing issue
| some printers print border on right/bottom edge of images
| 3.2.3.1
|-
| OPTION LANDSCAPE
| force landscape orientation for the form
|
| 2.6
|-
| OPTION SUMMARIZE_PRODUCTS
| summarize product totals when printing invoices
|
| 1.6.6
|-
| PDFPAGES n <nowiki>|</nowiki> ALL
| number of PDF document pages to include on form
| default is first page only
| 4.3.9.10
|-
| PRINTER name
| creates a virtual printer name
| Keystone can map this name to a physical printer with different settings per user
|
|-
| TITLE name
| descriptive name of this form
| some options display this to the user when selecting forms
|
|-
| VERSION n
| indicates the version number of the form
| used for special processing by some Keystone options
| 2.5.25
|-
| WIDTH n
| number of columns on the form
| increase as needed but keep in mind this will reduce the font size
|
|}

===Heading===
Information that prints 1 time at the top of the form.

Alternate headings (e.g. "HEADING 4") are used in certain types of forms for special sections of a form.

===Detail===
Information that repeats for each line of detail.

Certain forms may have alternate detail lines with unique behavior. This could be an alternate type of detail or sub-detail. e.g. "DETAIL 2" on an invoice is used to print comments.

===Total===
Information that prints at the bottom of the form.

{| border="3" cellspacing="0" cellpadding="3"
! Command
! Purpose
! Comment
! Keystone Version
|-
| NEWPAGE
| Start new page on a form
| Only verified for Total Section
| 3.3.1
|}

Sample Total with a NEWPAGE:
<PRE>
TOTAL

LINE 42

COLUMN 41
BOX 5,24,0,20
BOX 5,24
BOX 5,36
LINE +1 COLUMN 44 TEXT SUB TOTAL
COLUMN 65 FORMAT ######.00 FIELD CALC_SUBTOTAL

LINE +1 COLUMN 44 TEXT SALES TAX-
COLUMN 54 FIELD TAX_AUTHORITY
COLUMN 65 FORMAT ######.00 FIELD CALC_SALESTAX

LINE +1 COLUMN 44 TEXT TICKET TOTAL
COLUMN 65 FORMAT ######.00 FIELD CALC_TICKETTOTAL
NEWPAGE

LINE +2 COLUMN 1
LINE +1 COLUMN 30 TEXT *** WARNING ***
LINE +1 COLUMN 10 TEXT Cement is not good for you and It doesn't taste very good.
LINE +1 COLUMN 10 TEXT Do not eat cement or stuff made from cement. Do not eat
LINE +1 COLUMN 10 TEXT Tide Pods either.
LINE +1 COLUMN 1 LEFT IMAGE 2
! DoNotEatCement.jpg
LINE +3 COLUMN 13 TEXT RECEIVED BY:
COLUMN 26 TEXT ________________________________________
LINE +2 COLUMN 1
</PRE>

==Working With Forms==

===Formats===
<PRE>
LINE +1 COLUMN 1 FORMAT mm/dd/yy FIELD TICKET_DATE
COLUMN 10 RIGHT 7 FIELD TICKET_NO
COLUMN 18 FORMAT ####0.00 FIELD QTY_SOLD
COLUMN 27 FIELD UNIT_OF_MEASURE
</PRE>

*'''Date:''' The date April 5, 2018 with a format of '''mm/dd/yy''' will print as '''04/05/18''', '''mm/dd/yyyy''' as '''4/05/2018'''
*'''Right/Left''' Slide text to the right or left of the designated space.
*'''Numbers with # and 0:''' '''#''' is a placeholder that prints if needed. '''0''' will always print a value. Example: 403.25 printed with a format of '''####0.00''' prints as " 403.25", with a format of '''00000.00''' as "00403.25"

===Comments===
Lines that begin with a ! are comments. They can be removed as needed.
<PRE>
! AVAILABLE CALCULATED FIELDS
! ===========================
</PRE>

===Images===

In form Maintenance, select '''Load''' on the Images tab. 
[[Image:Frm ld img.png]]
Load the image.

When Setting up the form, refer to the image by number. The following code places an image in column 3, scaled to be 12 characters wide:
<PRE>
LINE 2 COLUMN 3
LEFT 12 IMAGE 2
</PRE>

===Conditions===
Conditions can be used to change the printed form logic, based on a field or form conditional value (Example 1.) When using "IF" with a field, the form will run the logic if the field is '''not''' null or zero (Example 2.)

You can nest "IF" statements with "ELSE" to do multiple condition checks (Example 3.) Insert the first "IF" condition, then use "ELSE" followed by another "IF" statement. Note: If "ELSE" is on the same line as "IF" it will give unintended results.

<PRE>
!EXAMPLE 1 -- Print "INTERNAL USE ONLY" if COND_INTERNAL is met.
IF COND_INTERNAL
COLUMN 8 TEXT INTERNAL USE ONLY
ENDIF

!EXAMPLE 2 -- Print UNIT_PRICE, if UNIT_PRICE is not null or zero.
IF UNIT_PRICE
COLUMN 16 FIELD UNIT_PRICE
ENDIF

!EXAMPLE 3 -- Print PRODUCT_COST if COND_INTERNAL is met, otherwise print UNIT_PCT_DISC if it is not null or zero. If COND_INTERNAL is not met and UNIT_PCT_DISC is null or zero, nothing will print.
! -- Note that only ONE "ENDIF" is used despite the use of TWO "IF" statements.
IF COND_INTERNAL
COLUMN 70 FORMAT ####.000 FIELD PRODUCT_COST
ELSE
IF UNIT_PCT_DISC
COLUMN 70 RIGHT 8 FIELD CALC_DISCOUNT
ENDIF
</PRE>

=== CHAIN command: Creating Multiple Forms ===
The Chain command allows multiple forms to print at one time. These forms can be identical or unique, and can print to multiple printers.

The Chain command is used in the FORM section.
Syntax: CHAIN [formname].FRM (e.g. CHAIN ARTCK.FRM)

In order to use multiple printers, make sure that the printer ALIAS is unique for each of the forms. Make sure to update the Plant to point to the correct form. Then in Ticket Printing/ Printer setup you can assign each alias to a printer.

When mixing a special form and a standard form, it is probably best to have the special form chain to the standard form. This prevents you from needing to create a new standard form and makes setting up the printers easier. The Printer setup develops the Alias list from the primary form for each plant. So if a special form with a unique alias is used as the primary form for a plant, then that Alias will appear on the list.

===Bar Codes===
Here is a section from a sample ticket form file that shows how to print barcodes on ticket forms.

NOTE that this should work in a similar way for dot-matrix (With EPSON emulation) and laser printers. However, for dot-matrix printers the only (currently) supported bar code format is Code 39. For laser/inkjet printers you must have a bar code font available on the printer, and you would specify that font name where you see “FONTNAME BARCODE39” in the sample below.

<PRE>
FORM
LENGTH 66 WIDTH 80 PRINTER ARTicket
FONTNAME VERDANA

HEADING
LINE 1 COLUMN 1
FONTNAME BARCODE39
FORMAT 00000000 FIELD TICKET_NO
FONTNAME DEFAULT

LINE 8 COLUMN 5 FIELD PLANT_NO
COLUMN 10 FORMAT #0":"00 FIELD TICKET_TIME
COLUMN 30 FIELD TRUCK_NO
COLUMN 38 FIELD DRIVER_NAME
COLUMN 58 FORMAT MM/DD/YY FIELD TICKET_DATE
COLUMN 71
</PRE>

===Boxes/Shading===

The BOX command may be used in any form printing section (Heading, Detail, Total.) The syntax is as follows:

<code>
BOX Height, Width [,Weight [,Shading [,Color]]]
</code>

Example:
<pre>BOX 1,76,0,20,clYellow</pre>

Height and Width are expressed in printed characters.

Weight is optional (default is 8 pixels) and indicates the number of pixels for the box border. The border is drawn in the current COLOR setting (black is default.)

Shading is optional (default is no shading) and specifies the shading percentage (0-100.) Lower shading is brighter color, higher shading is darker color.

(Keystone 3.6.4.7+) Color is optional (default is black) and specifies the shading color. The borders are drawn in the current font color.

When Color is black it is treated as white internally, meaning that a lower shading will tend toward white (no shading) while a higher shading will tend toward black.

==See Also==
:[[Keystone Form Colors]]
:[[Sample Forms]]
:[[Payroll: Form Versions]]
:[[Invoice Form Fields]]
:[[Ticket Form Fields]]
:[[AP Check Form Fields]]
:[[Quote Form Fields]]

Quote Form Fields

2025-06-25T19:39:27Z

Mbarker:

Quote form Fields
(Oct. 10, 2019 ver. 3.6)

Part of [[Keystone Forms]]

===Selected Fields===

<PRE>
CAST(' + IntToStr(i) + ' AS INTEGER) LOCPRODCLASS,
QH.PROSPECT_NO, QH.JOB_PO_LOC, QH.SALESPERSON, QC.D_AND_B_RATING,
QH.FOLLOW_UP_DATE, QH.WON_LOST_FLAG, QH.REASON_CODE,
QH.QUOTE_DATE, QH.LAST_REVISED_DATE,
QH.EXPIRATION_DATE, QH.SESSION_NO, QH.TRANS_NO, QD.LINE_NO,
QH.*, QD.*,
QC.NAME,
QC.ADDRESS_1,
QC.ADDRESS_2,
QC.CITY,
QC.STATE,
QC.ZIP,
QC.CLASS,
QC.D_AND_B_RATING,
QC.PHONE_NO CUST_PHONE_NO,
QC.FAX_NO CUST_FAX_NO,
(0) TAX_RATE,
SL.DESCRIPTION SLSPN_NAME,
SL.JOB_TITLE SLSPN_JOB_TITLE,
SL.PHONE_NO SLSPN_PHONE_NO,
SL.CELL_NO SLSPN_CELL_NO,
SL.FAX_NO SLSPN_FAX_NO,
SL.EMAIL SLSPN_EMAIL,
SL.USER_1 SLSPN_USER_1,
SL.USER_2 SLSPN_USER_2,
SL.SIGNATURE_IMAGE SL_SIGNATURE_IMAGE,
SL.SIGNATURE_IMAGE_EXT SL_SIGNATURE_IMAGE_EXT,
CT.DESCRIPTION TERMS_DESC,
PL.PLANT_NAME, PL.PLANT_SCREEN_ID,
PL.ADDRESS_1 PLANT_ADDRESS_1, PL.ADDRESS_2 PLANT_ADDRESS_2,
PL.PHONE_NO PLANT_PHONE_NO,
PR.PRODUCT_TYPE, PR.PLANT_NO PROD_PLANT_NO,
PL2.PLANT_NAME PROD_PLANT_NAME, PL2.PLANT_SCREEN_ID PROD_PLANT_SCREEN_ID,
UC.DESCRIPTION USAGE_DESC
FROM ' + VIEW_QTPROSP_CUST_LIST + ' QC
INNER JOIN ' + TBL_QTJOBHD + ' QH ON (QH.PROSPECT_NO = QC.PROSPECT_NO)
INNER JOIN ' + TBL_QTJOBDT + ' QD ON (QH.SESSION_NO = QD.SESSION_NO) AND (QH.TRANS_NO = QD.TRANS_NO)
LEFT OUTER JOIN ' + TBL_ARSLSPER + ' SL ON (QH.SALESPERSON = SL.CLASS_NO)
LEFT OUTER JOIN ' + TBL_ARCTMCLS + ' CT ON (QH.TERMS_CLASS = CT.CLASS_NO)
LEFT OUTER JOIN ' + TBL_ARPROD + ' PR ON (PR.PRODUCT_CODE = QD.PRODUCT_CODE)
LEFT OUTER JOIN ' + TBL_ARPLANT + ' PL ON (PL.PLANT_NO = QH.PLANT_NO)
LEFT OUTER JOIN ' + TBL_ARPLANT + ' PL2 ON (PL2.PLANT_NO = PR.PLANT_NO)
LEFT OUTER JOIN ' + TBL_DIUSECLS + ' UC ON (UC.CLASS_NO = QH.USAGE_TYPE)
PROD_DESCRIPTION_1 (4.7.4)
PROD_DESCRIPTION_2 (4.7.4)
</PRE>

===Calculated Fields===
<PRE>
CALC_CUSTADDR1
CALC_CUSTADDR2
CALC_CUSTADDR3
CALC_CUSTADDR4
CALC_RETADDR1
CALC_RETADDR2
CALC_RETADDR3
CALC_RETADDR4
CALC_SYSDATE
CALC_ORDTAXABLE
CALC_ORDNONTAX
CALC_ORDSUBTOTAL
CALC_ORDTAXTOTAL
CALC_ORDTOTAL
CALC_LISTSUBTOTAL
CALC_LISTTAXTOTAL
CALC_LISTTOTAL
CALC_SAVINGS
CALC_DISCOUNT
CALC_COSTTOTAL
CALC_PROFIT
COND_PRTRETADDR
COND_INTERNAL
COND_PRTLISTS
CALC_USERID
CALC_EXTPRICE
CALC_DISC_UNITPRICE
CALC_DISC_EXTPRICE
COND_COMMENT
CALC_DISCTOTAL
CALC_DISC_ORDSUBTOTAL
CALC_DISC_ORDTOTAL
CALC_UNIT_DISC
CALC_UNIT_TAX
CALC_UNIT_NET
CONDITION_1
CONDITION_2
CONDITION_3
CONDITION_4
CONDITION_5
CONDITION_6
CONDITION_7
CONDITION_8
CONDITIONS (LEFT 80 - FORMAT MEMO)
CALC_DISCTAXTOTAL
CALC_DISCTAX_ORDTOTAL
CALC_DISCSAVINGS
COND_PRODTYPE_MIX
COND_PRODTYPE_ING
COND_PRODTYPE_AGG
COND_PRODTYPE_DEL
CALC_UMS
CALC_UMSTOTAL
COND_PRODUCTTOTALS
CALC_UMSTOTALLINE (AFTER DETAIL)
CONTACT_EMAIL
</PRE>

===Salesperson Signature Image===

To print the salesperson's signature image on the quote form, use this line in the form file:

<pre>
COLUMN 1 LEFT 20 IMAGEFIELD SL_SIGNATURE SALESPERSON
^^^^^^^^^^^ -- the field in the quote table representing the Salesperson Id
^^^^^^^^^^^^ -- this specifies the salesperson signature image
^^ -- controls the horizontal width of the signature image
</pre>

Quote Form Fields

2025-06-25T19:39:14Z

Mbarker:

Quote form Fields
(Oct. 10, 2019 ver. 3.6)

Part of :[[Keystone Forms]]

===Selected Fields===

<PRE>
CAST(' + IntToStr(i) + ' AS INTEGER) LOCPRODCLASS,
QH.PROSPECT_NO, QH.JOB_PO_LOC, QH.SALESPERSON, QC.D_AND_B_RATING,
QH.FOLLOW_UP_DATE, QH.WON_LOST_FLAG, QH.REASON_CODE,
QH.QUOTE_DATE, QH.LAST_REVISED_DATE,
QH.EXPIRATION_DATE, QH.SESSION_NO, QH.TRANS_NO, QD.LINE_NO,
QH.*, QD.*,
QC.NAME,
QC.ADDRESS_1,
QC.ADDRESS_2,
QC.CITY,
QC.STATE,
QC.ZIP,
QC.CLASS,
QC.D_AND_B_RATING,
QC.PHONE_NO CUST_PHONE_NO,
QC.FAX_NO CUST_FAX_NO,
(0) TAX_RATE,
SL.DESCRIPTION SLSPN_NAME,
SL.JOB_TITLE SLSPN_JOB_TITLE,
SL.PHONE_NO SLSPN_PHONE_NO,
SL.CELL_NO SLSPN_CELL_NO,
SL.FAX_NO SLSPN_FAX_NO,
SL.EMAIL SLSPN_EMAIL,
SL.USER_1 SLSPN_USER_1,
SL.USER_2 SLSPN_USER_2,
SL.SIGNATURE_IMAGE SL_SIGNATURE_IMAGE,
SL.SIGNATURE_IMAGE_EXT SL_SIGNATURE_IMAGE_EXT,
CT.DESCRIPTION TERMS_DESC,
PL.PLANT_NAME, PL.PLANT_SCREEN_ID,
PL.ADDRESS_1 PLANT_ADDRESS_1, PL.ADDRESS_2 PLANT_ADDRESS_2,
PL.PHONE_NO PLANT_PHONE_NO,
PR.PRODUCT_TYPE, PR.PLANT_NO PROD_PLANT_NO,
PL2.PLANT_NAME PROD_PLANT_NAME, PL2.PLANT_SCREEN_ID PROD_PLANT_SCREEN_ID,
UC.DESCRIPTION USAGE_DESC
FROM ' + VIEW_QTPROSP_CUST_LIST + ' QC
INNER JOIN ' + TBL_QTJOBHD + ' QH ON (QH.PROSPECT_NO = QC.PROSPECT_NO)
INNER JOIN ' + TBL_QTJOBDT + ' QD ON (QH.SESSION_NO = QD.SESSION_NO) AND (QH.TRANS_NO = QD.TRANS_NO)
LEFT OUTER JOIN ' + TBL_ARSLSPER + ' SL ON (QH.SALESPERSON = SL.CLASS_NO)
LEFT OUTER JOIN ' + TBL_ARCTMCLS + ' CT ON (QH.TERMS_CLASS = CT.CLASS_NO)
LEFT OUTER JOIN ' + TBL_ARPROD + ' PR ON (PR.PRODUCT_CODE = QD.PRODUCT_CODE)
LEFT OUTER JOIN ' + TBL_ARPLANT + ' PL ON (PL.PLANT_NO = QH.PLANT_NO)
LEFT OUTER JOIN ' + TBL_ARPLANT + ' PL2 ON (PL2.PLANT_NO = PR.PLANT_NO)
LEFT OUTER JOIN ' + TBL_DIUSECLS + ' UC ON (UC.CLASS_NO = QH.USAGE_TYPE)
PROD_DESCRIPTION_1 (4.7.4)
PROD_DESCRIPTION_2 (4.7.4)
</PRE>

===Calculated Fields===
<PRE>
CALC_CUSTADDR1
CALC_CUSTADDR2
CALC_CUSTADDR3
CALC_CUSTADDR4
CALC_RETADDR1
CALC_RETADDR2
CALC_RETADDR3
CALC_RETADDR4
CALC_SYSDATE
CALC_ORDTAXABLE
CALC_ORDNONTAX
CALC_ORDSUBTOTAL
CALC_ORDTAXTOTAL
CALC_ORDTOTAL
CALC_LISTSUBTOTAL
CALC_LISTTAXTOTAL
CALC_LISTTOTAL
CALC_SAVINGS
CALC_DISCOUNT
CALC_COSTTOTAL
CALC_PROFIT
COND_PRTRETADDR
COND_INTERNAL
COND_PRTLISTS
CALC_USERID
CALC_EXTPRICE
CALC_DISC_UNITPRICE
CALC_DISC_EXTPRICE
COND_COMMENT
CALC_DISCTOTAL
CALC_DISC_ORDSUBTOTAL
CALC_DISC_ORDTOTAL
CALC_UNIT_DISC
CALC_UNIT_TAX
CALC_UNIT_NET
CONDITION_1
CONDITION_2
CONDITION_3
CONDITION_4
CONDITION_5
CONDITION_6
CONDITION_7
CONDITION_8
CONDITIONS (LEFT 80 - FORMAT MEMO)
CALC_DISCTAXTOTAL
CALC_DISCTAX_ORDTOTAL
CALC_DISCSAVINGS
COND_PRODTYPE_MIX
COND_PRODTYPE_ING
COND_PRODTYPE_AGG
COND_PRODTYPE_DEL
CALC_UMS
CALC_UMSTOTAL
COND_PRODUCTTOTALS
CALC_UMSTOTALLINE (AFTER DETAIL)
CONTACT_EMAIL
</PRE>

===Salesperson Signature Image===

To print the salesperson's signature image on the quote form, use this line in the form file:

<pre>
COLUMN 1 LEFT 20 IMAGEFIELD SL_SIGNATURE SALESPERSON
^^^^^^^^^^^ -- the field in the quote table representing the Salesperson Id
^^^^^^^^^^^^ -- this specifies the salesperson signature image
^^ -- controls the horizontal width of the signature image
</pre>

Keystone Forms

2025-06-25T19:36:56Z

Mbarker: /* Formats */

[[CATEGORY: FORMS]]

While forms can be stored in the customer directory (e.g. ...\cust\forms), this should only be done if the form is specific to a computer. Custom Forms belong in the database.

==Sections==
===Form Section===

{| border="3" cellspacing="0" cellpadding="3"
! Command
! Purpose
! Comment
! Keystone Version
|-
| BEGINCOPY n
| apply block of form only for nth copy
| applies to all form sections
| 2.7.16
|-
| CHAIN name
| the next form in the chain
|
|
|-
| COLUMNS n
| number of columns on each form
| used for labels
|
|-
| COPIES n
| number of copies of each form
|
|
|-
| CPI n
| characters per inch
|
|
|-
| ENDCOPY
| indicates end of COPY block
|
| 2.7.16
|-
| FONTNAME name
| default font for the form
|
|
|-
| LENGTH n
| number of lines on the form
| impacts automatic page breaks
|
|-
| LINES n
| number of lines for each label
| used for labels
|
|-
| LPI n
| lines per inch
|
|
|-
| MARGIN top,left,bottom,right
| specify page margins
| default is no margins
| 3.6.18.1
|-
| OPTION EXTEND_DETAIL
| allow form detail to extend into footer area
|
| 2.1.4
|-
| OPTION IMAGE_FIX
| fix image drawing issue
| some printers print border on right/bottom edge of images
| 3.2.3.1
|-
| OPTION LANDSCAPE
| force landscape orientation for the form
|
| 2.6
|-
| OPTION SUMMARIZE_PRODUCTS
| summarize product totals when printing invoices
|
| 1.6.6
|-
| PDFPAGES n <nowiki>|</nowiki> ALL
| number of PDF document pages to include on form
| default is first page only
| 4.3.9.10
|-
| PRINTER name
| creates a virtual printer name
| Keystone can map this name to a physical printer with different settings per user
|
|-
| TITLE name
| descriptive name of this form
| some options display this to the user when selecting forms
|
|-
| VERSION n
| indicates the version number of the form
| used for special processing by some Keystone options
| 2.5.25
|-
| WIDTH n
| number of columns on the form
| increase as needed but keep in mind this will reduce the font size
|
|}

===Heading===
Information that prints 1 time at the top of the form.

Alternate headings (e.g. "HEADING 4") are used in certain types of forms for special sections of a form.

===Detail===
Information that repeats for each line of detail.

Certain forms may have alternate detail lines with unique behavior. This could be an alternate type of detail or sub-detail. e.g. "DETAIL 2" on an invoice is used to print comments.

===Total===
Information that prints at the bottom of the form.

{| border="3" cellspacing="0" cellpadding="3"
! Command
! Purpose
! Comment
! Keystone Version
|-
| NEWPAGE
| Start new page on a form
| Only verified for Total Section
| 3.3.1
|}

Sample Total with a NEWPAGE:
<PRE>
TOTAL

LINE 42

COLUMN 41
BOX 5,24,0,20
BOX 5,24
BOX 5,36
LINE +1 COLUMN 44 TEXT SUB TOTAL
COLUMN 65 FORMAT ######.00 FIELD CALC_SUBTOTAL

LINE +1 COLUMN 44 TEXT SALES TAX-
COLUMN 54 FIELD TAX_AUTHORITY
COLUMN 65 FORMAT ######.00 FIELD CALC_SALESTAX

LINE +1 COLUMN 44 TEXT TICKET TOTAL
COLUMN 65 FORMAT ######.00 FIELD CALC_TICKETTOTAL
NEWPAGE

LINE +2 COLUMN 1
LINE +1 COLUMN 30 TEXT *** WARNING ***
LINE +1 COLUMN 10 TEXT Cement is not good for you and It doesn't taste very good.
LINE +1 COLUMN 10 TEXT Do not eat cement or stuff made from cement. Do not eat
LINE +1 COLUMN 10 TEXT Tide Pods either.
LINE +1 COLUMN 1 LEFT IMAGE 2
! DoNotEatCement.jpg
LINE +3 COLUMN 13 TEXT RECEIVED BY:
COLUMN 26 TEXT ________________________________________
LINE +2 COLUMN 1
</PRE>

==Working With Forms==

===Formats===
<PRE>
LINE +1 COLUMN 1 FORMAT mm/dd/yy FIELD TICKET_DATE
COLUMN 10 RIGHT 7 FIELD TICKET_NO
COLUMN 18 FORMAT ####0.00 FIELD QTY_SOLD
COLUMN 27 FIELD UNIT_OF_MEASURE
</PRE>

*'''Date:''' The date April 5, 2018 with a format of '''mm/dd/yy''' will print as '''04/05/18''', '''mm/dd/yyyy''' as '''4/05/2018'''
*'''Right/Left''' Slide text to the right or left of the designated space.
*'''Numbers with # and 0:''' '''#''' is a placeholder that prints if needed. '''0''' will always print a value. Example: 403.25 printed with a format of '''####0.00''' prints as " 403.25", with a format of '''00000.00''' as "00403.25"

===Comments===
Lines that begin with a ! are comments. They can be removed as needed.
<PRE>
! AVAILABLE CALCULATED FIELDS
! ===========================
</PRE>

===Images===

In form Maintenance, select '''Load''' on the Images tab. 
[[Image:Frm ld img.png]]
Load the image.

When Setting up the form, refer to the image by number. The following code places an image in column 3, scaled to be 12 characters wide:
<PRE>
LINE 2 COLUMN 3
LEFT 12 IMAGE 2
</PRE>

===Conditions===
Conditions can be used to change the printed form logic, based on a field or form conditional value (Example 1.) When using "IF" with a field, the form will run the logic if the field is '''not''' null or zero (Example 2.)

You can nest "IF" statements with "ELSE" to do multiple condition checks (Example 3.) Insert the first "IF" condition, then use "ELSE" followed by another "IF" statement. Note: If "ELSE" is on the same line as "IF" it will give unintended results.

<PRE>
!EXAMPLE 1 -- Print "INTERNAL USE ONLY" if COND_INTERNAL is met.
IF COND_INTERNAL
COLUMN 8 TEXT INTERNAL USE ONLY
ENDIF

!EXAMPLE 2 -- Print UNIT_PRICE, if UNIT_PRICE is not null or zero.
IF UNIT_PRICE
COLUMN 16 FIELD UNIT_PRICE
ENDIF

!EXAMPLE 3 -- Print PRODUCT_COST if COND_INTERNAL is met, otherwise print UNIT_PCT_DISC if it is not null or zero. If COND_INTERNAL is not met and UNIT_PCT_DISC is null or zero, nothing will print.
! -- Note that only ONE "ENDIF" is used despite the use of TWO "IF" statements.
IF COND_INTERNAL
COLUMN 70 FORMAT ####.000 FIELD PRODUCT_COST
ELSE
IF UNIT_PCT_DISC
COLUMN 70 RIGHT 8 FIELD CALC_DISCOUNT
ENDIF
</PRE>

=== CHAIN command: Creating Multiple Forms ===
The Chain command allows multiple forms to print at one time. These forms can be identical or unique, and can print to multiple printers.

The Chain command is used in the FORM section.
Syntax: CHAIN [formname].FRM (e.g. CHAIN ARTCK.FRM)

In order to use multiple printers, make sure that the printer ALIAS is unique for each of the forms. Make sure to update the Plant to point to the correct form. Then in Ticket Printing/ Printer setup you can assign each alias to a printer.

When mixing a special form and a standard form, it is probably best to have the special form chain to the standard form. This prevents you from needing to create a new standard form and makes setting up the printers easier. The Printer setup develops the Alias list from the primary form for each plant. So if a special form with a unique alias is used as the primary form for a plant, then that Alias will appear on the list.

===Bar Codes===
Here is a section from a sample ticket form file that shows how to print barcodes on ticket forms.

NOTE that this should work in a similar way for dot-matrix (With EPSON emulation) and laser printers. However, for dot-matrix printers the only (currently) supported bar code format is Code 39. For laser/inkjet printers you must have a bar code font available on the printer, and you would specify that font name where you see “FONTNAME BARCODE39” in the sample below.

<PRE>
FORM
LENGTH 66 WIDTH 80 PRINTER ARTicket
FONTNAME VERDANA

HEADING
LINE 1 COLUMN 1
FONTNAME BARCODE39
FORMAT 00000000 FIELD TICKET_NO
FONTNAME DEFAULT

LINE 8 COLUMN 5 FIELD PLANT_NO
COLUMN 10 FORMAT #0":"00 FIELD TICKET_TIME
COLUMN 30 FIELD TRUCK_NO
COLUMN 38 FIELD DRIVER_NAME
COLUMN 58 FORMAT MM/DD/YY FIELD TICKET_DATE
COLUMN 71
</PRE>

===Boxes/Shading===

The BOX command may be used in any form printing section (Heading, Detail, Total.) The syntax is as follows:

<code>
BOX Height, Width [,Weight [,Shading [,Color]]]
</code>

Example:
<pre>BOX 1,76,0,20,clYellow</pre>

Height and Width are expressed in printed characters.

Weight is optional (default is 8 pixels) and indicates the number of pixels for the box border. The border is drawn in the current COLOR setting (black is default.)

Shading is optional (default is no shading) and specifies the shading percentage (0-100.) Lower shading is brighter color, higher shading is darker color.

(Keystone 3.6.4.7+) Color is optional (default is black) and specifies the shading color. The borders are drawn in the current font color.

When Color is black it is treated as white internally, meaning that a lower shading will tend toward white (no shading) while a higher shading will tend toward black.

==See Also==
:[[Keystone Form Colors]]
:[[Sample Forms]]
:[[Payroll: Form Versions]]
:[[Invoice Form Fields]]
:[[Ticket Form Fields]]
:[[AP Check Form Fields]]
:[[Quote Form Fields]]

Keystone Forms

2025-06-25T19:35:42Z

Mbarker:

[[CATEGORY: FORMS]]

While forms can be stored in the customer directory (e.g. ...\cust\forms), this should only be done if the form is specific to a computer. Custom Forms belong in the database.

==Sections==
===Form Section===

{| border="3" cellspacing="0" cellpadding="3"
! Command
! Purpose
! Comment
! Keystone Version
|-
| BEGINCOPY n
| apply block of form only for nth copy
| applies to all form sections
| 2.7.16
|-
| CHAIN name
| the next form in the chain
|
|
|-
| COLUMNS n
| number of columns on each form
| used for labels
|
|-
| COPIES n
| number of copies of each form
|
|
|-
| CPI n
| characters per inch
|
|
|-
| ENDCOPY
| indicates end of COPY block
|
| 2.7.16
|-
| FONTNAME name
| default font for the form
|
|
|-
| LENGTH n
| number of lines on the form
| impacts automatic page breaks
|
|-
| LINES n
| number of lines for each label
| used for labels
|
|-
| LPI n
| lines per inch
|
|
|-
| MARGIN top,left,bottom,right
| specify page margins
| default is no margins
| 3.6.18.1
|-
| OPTION EXTEND_DETAIL
| allow form detail to extend into footer area
|
| 2.1.4
|-
| OPTION IMAGE_FIX
| fix image drawing issue
| some printers print border on right/bottom edge of images
| 3.2.3.1
|-
| OPTION LANDSCAPE
| force landscape orientation for the form
|
| 2.6
|-
| OPTION SUMMARIZE_PRODUCTS
| summarize product totals when printing invoices
|
| 1.6.6
|-
| PDFPAGES n <nowiki>|</nowiki> ALL
| number of PDF document pages to include on form
| default is first page only
| 4.3.9.10
|-
| PRINTER name
| creates a virtual printer name
| Keystone can map this name to a physical printer with different settings per user
|
|-
| TITLE name
| descriptive name of this form
| some options display this to the user when selecting forms
|
|-
| VERSION n
| indicates the version number of the form
| used for special processing by some Keystone options
| 2.5.25
|-
| WIDTH n
| number of columns on the form
| increase as needed but keep in mind this will reduce the font size
|
|}

===Heading===
Information that prints 1 time at the top of the form.

Alternate headings (e.g. "HEADING 4") are used in certain types of forms for special sections of a form.

===Detail===
Information that repeats for each line of detail.

Certain forms may have alternate detail lines with unique behavior. This could be an alternate type of detail or sub-detail. e.g. "DETAIL 2" on an invoice is used to print comments.

===Total===
Information that prints at the bottom of the form.

{| border="3" cellspacing="0" cellpadding="3"
! Command
! Purpose
! Comment
! Keystone Version
|-
| NEWPAGE
| Start new page on a form
| Only verified for Total Section
| 3.3.1
|}

Sample Total with a NEWPAGE:
<PRE>
TOTAL

LINE 42

COLUMN 41
BOX 5,24,0,20
BOX 5,24
BOX 5,36
LINE +1 COLUMN 44 TEXT SUB TOTAL
COLUMN 65 FORMAT ######.00 FIELD CALC_SUBTOTAL

LINE +1 COLUMN 44 TEXT SALES TAX-
COLUMN 54 FIELD TAX_AUTHORITY
COLUMN 65 FORMAT ######.00 FIELD CALC_SALESTAX

LINE +1 COLUMN 44 TEXT TICKET TOTAL
COLUMN 65 FORMAT ######.00 FIELD CALC_TICKETTOTAL
NEWPAGE

LINE +2 COLUMN 1
LINE +1 COLUMN 30 TEXT *** WARNING ***
LINE +1 COLUMN 10 TEXT Cement is not good for you and It doesn't taste very good.
LINE +1 COLUMN 10 TEXT Do not eat cement or stuff made from cement. Do not eat
LINE +1 COLUMN 10 TEXT Tide Pods either.
LINE +1 COLUMN 1 LEFT IMAGE 2
! DoNotEatCement.jpg
LINE +3 COLUMN 13 TEXT RECEIVED BY:
COLUMN 26 TEXT ________________________________________
LINE +2 COLUMN 1
</PRE>

==Working With Forms==

===Formats===
<PRE>
LINE +1 COLUMN 1 FORMAT mm/dd/yy FIELD TICKET_DATE
COLUMN 10 RIGHT 7 FIELD TICKET_NO
COLUMN 18 FORMAT ####0.00 FIELD QTY_SOLD
COLUMN 27 FIELD UNIT_OF_MEASURE
</PRE>

*'''Date:''' The date April 5, 2018 with a format of '''mm/dd/yy''' will print as '''04/05/2018''', '''mm/dd/yyyy''' as '''4/05/2018'''
*'''Right/Left''' Slide text to the right or left of the designated space.
*'''Numbers with # and 0:''' '''#''' is a placeholder that prints if needed. '''0''' will always print a value. Example: 403.25 printed with a format of '''####0.00''' prints as " 403.25", with a format of '''00000.00''' as "00403.25"

===Comments===
Lines that begin with a ! are comments. They can be removed as needed.
<PRE>
! AVAILABLE CALCULATED FIELDS
! ===========================
</PRE>

===Images===

In form Maintenance, select '''Load''' on the Images tab. 
[[Image:Frm ld img.png]]
Load the image.

When Setting up the form, refer to the image by number. The following code places an image in column 3, scaled to be 12 characters wide:
<PRE>
LINE 2 COLUMN 3
LEFT 12 IMAGE 2
</PRE>

===Conditions===
Conditions can be used to change the printed form logic, based on a field or form conditional value (Example 1.) When using "IF" with a field, the form will run the logic if the field is '''not''' null or zero (Example 2.)

You can nest "IF" statements with "ELSE" to do multiple condition checks (Example 3.) Insert the first "IF" condition, then use "ELSE" followed by another "IF" statement. Note: If "ELSE" is on the same line as "IF" it will give unintended results.

<PRE>
!EXAMPLE 1 -- Print "INTERNAL USE ONLY" if COND_INTERNAL is met.
IF COND_INTERNAL
COLUMN 8 TEXT INTERNAL USE ONLY
ENDIF

!EXAMPLE 2 -- Print UNIT_PRICE, if UNIT_PRICE is not null or zero.
IF UNIT_PRICE
COLUMN 16 FIELD UNIT_PRICE
ENDIF

!EXAMPLE 3 -- Print PRODUCT_COST if COND_INTERNAL is met, otherwise print UNIT_PCT_DISC if it is not null or zero. If COND_INTERNAL is not met and UNIT_PCT_DISC is null or zero, nothing will print.
! -- Note that only ONE "ENDIF" is used despite the use of TWO "IF" statements.
IF COND_INTERNAL
COLUMN 70 FORMAT ####.000 FIELD PRODUCT_COST
ELSE
IF UNIT_PCT_DISC
COLUMN 70 RIGHT 8 FIELD CALC_DISCOUNT
ENDIF
</PRE>

=== CHAIN command: Creating Multiple Forms ===
The Chain command allows multiple forms to print at one time. These forms can be identical or unique, and can print to multiple printers.

The Chain command is used in the FORM section.
Syntax: CHAIN [formname].FRM (e.g. CHAIN ARTCK.FRM)

In order to use multiple printers, make sure that the printer ALIAS is unique for each of the forms. Make sure to update the Plant to point to the correct form. Then in Ticket Printing/ Printer setup you can assign each alias to a printer.

When mixing a special form and a standard form, it is probably best to have the special form chain to the standard form. This prevents you from needing to create a new standard form and makes setting up the printers easier. The Printer setup develops the Alias list from the primary form for each plant. So if a special form with a unique alias is used as the primary form for a plant, then that Alias will appear on the list.

===Bar Codes===
Here is a section from a sample ticket form file that shows how to print barcodes on ticket forms.

NOTE that this should work in a similar way for dot-matrix (With EPSON emulation) and laser printers. However, for dot-matrix printers the only (currently) supported bar code format is Code 39. For laser/inkjet printers you must have a bar code font available on the printer, and you would specify that font name where you see “FONTNAME BARCODE39” in the sample below.

<PRE>
FORM
LENGTH 66 WIDTH 80 PRINTER ARTicket
FONTNAME VERDANA

HEADING
LINE 1 COLUMN 1
FONTNAME BARCODE39
FORMAT 00000000 FIELD TICKET_NO
FONTNAME DEFAULT

LINE 8 COLUMN 5 FIELD PLANT_NO
COLUMN 10 FORMAT #0":"00 FIELD TICKET_TIME
COLUMN 30 FIELD TRUCK_NO
COLUMN 38 FIELD DRIVER_NAME
COLUMN 58 FORMAT MM/DD/YY FIELD TICKET_DATE
COLUMN 71
</PRE>

===Boxes/Shading===

The BOX command may be used in any form printing section (Heading, Detail, Total.) The syntax is as follows:

<code>
BOX Height, Width [,Weight [,Shading [,Color]]]
</code>

Example:
<pre>BOX 1,76,0,20,clYellow</pre>

Height and Width are expressed in printed characters.

Weight is optional (default is 8 pixels) and indicates the number of pixels for the box border. The border is drawn in the current COLOR setting (black is default.)

Shading is optional (default is no shading) and specifies the shading percentage (0-100.) Lower shading is brighter color, higher shading is darker color.

(Keystone 3.6.4.7+) Color is optional (default is black) and specifies the shading color. The borders are drawn in the current font color.

When Color is black it is treated as white internally, meaning that a lower shading will tend toward white (no shading) while a higher shading will tend toward black.

==See Also==
:[[Keystone Form Colors]]
:[[Sample Forms]]
:[[Payroll: Form Versions]]
:[[Invoice Form Fields]]
:[[Ticket Form Fields]]
:[[AP Check Form Fields]]
:[[Quote Form Fields]]