Returns the tmp_inv.quantity and sets the printer to print the specified quantity.

Used only when designing a layout for the Cognitive printer. It extracts the quantity of tickets that the customer purchased on a single line item and prints that amount of identical tickets. The ticket designer types the data field name tmp_qty or a number between the parentheses to let the function know how many tickets to print.

 

If ten tickets or vouchers are sold on a single line item in Sales, ticketqty(tmp_qty) prints ten identical tickets. The following is an example of the first line of a Cognitive Ticket layout:

This code prints one or more tickets or vouchers on a Cognitive printer, depending on the quantity sold on a particular invoice line item.

This code prints one ticket on a Cognitive printer.

ticketqty(5) returns 5

Custom

Returns the ticket start date and ticket end date as (day of week) MM/DD as a string.

Designed to be used in multi-day Ticket layouts and uses the fields Tmp_date and Tmp_edate to produce the first three letters of the day of the week, the number of the month and the year. Tmp_date is the date that the ticket can start being used. Tmp_edate is the last date the ticket can be used. If the ticket was purchased for one day only, the start date prints. If the ticket was purchased for more than one day, the start and end dates print.

 

If the ticket was purchased on Monday, April 1, GETDATESTRING() returns MON 04/01 if the ticket was purchased for one day. GETDATESTRING()results in MON 04/01 - FRI 04/05 if the ticket was purchased for more than one day.

Custom

Returns the payment types used and the breakdown of the purchase as a string.

 

FOP_BREAK()returns:

Returns the payment breakdown used at the time of the purchase, as a string.

Displays the form(s) of payment used to pay for the sale.

If Visa and cash were used to pay for the sale, VISA+CASH are displayed.

Converts a date to the literal name of the month.

 

CMONTH(DATE()) returns April if the current month is 04.

Extracts the day of week from the date passed in and returns the day of week as a literal string.

 

Tests an argument (depending on the type) for true or false, zero or non_zero, blank or non_blank and returns a 1 if empty and 0 if not empty.

This function can be used only with the if() function or the iif() VFP function.

Returns the daily code from the dailycode database using the date that was entered as the parameter.

 

DAILYCODE(CTOD(TMP_DATE)) returns the daily code for the date that the ticket or voucher was sold. Because TMP_DATE is a character date field, it must be converted into a date value using the CTOD() VFP function. DAILYCODE(DATE()) returns the daily code for the current date.

Tests argument 1 for true or false; returns argument 2 if true or argument 3 if false.

When using this function the ticket designer uses a data field or logical expression to be tested for the first parameter. The second and third parameters of this function can contain legal VFP functions/expressions, other Salesware custom functions or a combination of legal VFP functions/expressions and Salesware custom functions.

 

Returns the time in the form of a character string that has been altered by having hours or minutes added or subtracted and the time rounded and limited according to minimums and maximums for each day of the week. The time is returned in twelve hour clock form only. This function accepts up to nineteen parameters.

 

Note: This function was designed to accommodate time-based tickets. If an area allows a customer to buy a two or four-hour ticket, this function allows the ticket designer to specify the hours of business, provide for time-in-line, putting on skis, etc.

 

 

Assuming today is Friday and the current time is 07:00, 10:00 am is returned.

Assuming today is Friday and a current time is 10:06, 12:15 pm is returned.

Assuming today is Friday and the current time is 24:30, 02:00 am is returned.

<expN1> - Number of hours to add or subtract. To add hours, enter a positive number. To subtract hours, enter a negative number.

<expN2> - Number of minutes to add or subtract. To add minutes, enter a positive number. To subtract minutes, enter a negative number.

<expN3> - Number of minutes to round up to.

<expN4> - Number of minutes at which to start rounding.

<expC2> through <expC8> − Maximum time to be returned for a day. <expC2> is Sunday’s maximum while <expC8> is Saturday’s maximum. Enter the string as a time (HH:MM). To set the maximum for a day to be some time during the following day (i.e., after midnight), enter the time as a military time, accounting for moving beyond midnight.

 

To set the maximum for 2:00 AM the following day, enter 26:00 as the maximum. <expC9> through <expC15> follow the same format but are the minimum times.

Encodes the base 10 number into a base 38 number, primarily for compression of barcodes.

 

Encodes the base 10 character date into a base 38 number, primarily for compression of barcodes.

 

ENCRYPT_DATE(TMP_EDATE) where TMP_EDATE = 12/25/2002 returns CP (C=12 and P=25 in base 38). ENCRYPT_DATE(DTOC(DATE())) encrypts the current date.

Parses and formats the specified text for printing on a dot matrix printer. Used in layouts designed for dot matrix printers only. If the printer at the salespoint is a dot matrix printer, this function must be used on every line of the Ticket layout. SHOW()sends the printer an escape sequence before printing each line of the ticket, which specifies fonts, font sizes and font styles. The justification of a line of text (right, center, left) can also be specified.

<style1> through <style4> − The font styles are available to the ticket designer when designing tickets for a dot matrix printer. Availability of specific styles is dependent on the brand of the printer. Can be any of the following:

nlq_print (near letter-quality print )

 

<alignment> − can be:

 

<line size> − The number of characters on the line that is being printed.

 

<VFP expr> − A VFP expression that specifies what is to be printed on the line.

 

Ticket/Voucher layouts use TTOC() (time to character) followed by specifications for the desired format.

%a       Abbreviated weekday name

%A      Full weekday name       

%b       Abbreviated month name

%B       Full month name

%c       Date and time representation appropriate for
locale

%d       Day of month as decimal number (01 - 31)

%H       Hour in 24-hour format (00 - 23)

%I       Hour in 12-hour format (01 - 12)

%j       Day of year as decimal number (001 - 366)

%m      Month as decimal number (01 - 12)

%M      Minute as decimal number (00 - 59)

%p      Current locale’s A.M./P.M. indicator for 12-
hour clock

%S       Second as decimal number (00 - 59)

%U       Week of year as decimal number, with
Sunday as first day of week (00 - 53)

%w       Weekday as decimal number (0 - 6; Sunday
is 0)

%W      Week of year as decimal number, with
Monday as first day of week (00 - 53)

%x     Date representation for current locale

%X       Time representation for current locale

%y       Year without century, as decimal number (00
- 99)

%Y     Year with century, as decimal number

%Z Time-zone name; no characters if time zone
is unknown

%%      Percent sign

 

To print the transaction date & time in DD/MM/YYYY HH:MM:SS AM/PM format, you would use:

TTOC(alltrans->date_time,'%m/%d/%Y %I:%M:%S %p') results in 10/24/2005 12:30:45 PM

To print the transaction date and time in DD/MM/YYYY HH:MM:SS AM/PM format, you would use:

TTOC(alltrans->date_time,'%d/%m/%Y %I:%M:%S %p') results in 24/10/2005 12:30:45 PM

Prints the department description on tickets.

Prints the category description on tickets.