header-kbase.gif (5507 bytes)
button-dealers.gif (2310 bytes) button-download.gif (2472 bytes) button-kbase.gif (2239 bytes)
 

 

Touchnet File Formats

Last edited: December 15, 2003 08:08 AM

 

  This document contains a description for the format of several TouchNet related files. These file formats are subject to change without notice.

????.CHK file format

  All open checks when stored are assigned a file, with the name being the 4 digit CheckID (Padded with 0's) and the .CHK extension in the
  \Checks directory. This file is created with a proprietary binary model.  Below is a table listing the variables found in the file. The type
  and #Bytes indicate how to read the variable. The Offset indicates the position in the file that the information can be found.
  Integers and Long Integers are stored in LSB,MSB order. Strings are padded with spaces. All dollar amounts are stored as integers, in
  pennies format.  To display simply divide by 100.
   Variable
                    Type
       #Bytes
        Offset
StartTime
               Integer
         2
        0
ServerID
               Integer
         2
        2
TableNo
               String
         3
        4
CoverNo
               Integer
         2
        7
TaxesOn
               Integer
         2
        9
ChkItems
               Integer
         2
        11
  --------
(This section repeats 'ChkItems' times)
        
PLU
               Integer
         2
        13+(Item#-1)*10
Reserved
               Integer
         2
        15+(Item#-1)*10
Price
               Long Integer
         4
        19+(Item#-1)*10
Info
               Integer
         2
        21+(Item#-1)*10
  --------
 
ServerDept
               Integer
         2
        Len-440
CustomerName
               String
         10
        Len-438
CustomerRec
               Integer
         2
        Len-428
OrderType
               String
         8
        Len-426
Media1Amt
               Long Integer
         4
        Len-418
Media2Amt
               Long Integer
         4
        Len-414
MediaMethods
               Integer
         2
        Len-410
SplitSeat
               Integer
         2
        Len-408
Gratuity
               Integer
         2
        Len-406
Dollar1
               Long Integer
         4
        Len-404
Number1
               Long Integer
         4
        Len-400
Word1
               String
         6
        Len-396
Dollar2
               Long Integer
         4
        Len-390
Number2
               Long Integer
         4
        Len-386
Word2
               String
         6
        Len-382
Dollar3
               Long Integer
         4
        Len-376
Number3
               Long Integer
         4
        Len-372
Word3
               String
         6
        Len-368
Memo1
               String
         40
        Len-362
Memo2
               String
         40
        Len-322
Memo3
               String
         40
        Len-282
CheckAmount
               Long Integer
         4
        Len-242
Reserved
               String
         238  (0's)
        Len-238

Checks.DAT format

  The purpose of Checks.DAT is to serve as a quick look-up or index for all open checks. The information stored in this file, is for reference only, as the .CHK file contains the information that is actually retrieved with a check. The secondary purpose of this file, is to insure that a check is in use on only one node at a time. For this sake, a field called 'Node' will contain the name of the node that has the check, or '________' if it is not in use. The Checks.DAT file will grow as new checks are added. When a check is removed, it's record is replaced by all spaces (character 32) and a right justified '0' in the CheckID field. This tells TouchNet that this space is available to be reclaimed for another check.
Each record is 150 bytes. Within the record, each field is followed by a space (character 32). All numeric fields are stored as strings, ready to be displayed without modification. Here is the record format:

 

      Field
      Length
       Note
Node
       8
 
CheckID
       4
Must be "   0" if empty space
Table
       3
 
Server
       16
Server Name
Seat 
       2
Seat that check was split from (if any)
OrderType
       8
 
CustomerName
       10
 
Cus:Name
       16
 
Cus:Street
       20
 
Word1
       6
 
Number1
       5
 
Memo1
       40
 
  Note: Remember, each field is followed by a character 32!

YYMMDD.TIM File format

 Variable
     Type
       #Bytes
      Offset
EmployeeID
       Integer
        2
          0
Department
       Integer
        2
          2
TimeIn
       Integer
        2
          4
TimeOut
       Integer
        2
          6

TimeIn.DAT File Format

Variable
         Type
   #Bytes
      Offset
    Date
Long Integer
       4
        0
    TimeIn
Integer
       2
        4
    EmployeeID
Integer
       2
        6
    Department
Integer
       2
        8

Related Documents

Journal File Format

THIS DOCUMENT IS PROVIDED BY HOSPITALITY DATA SYSTEMS INC. FOR USE BY ITS APPROVED DEALERS AND DISTRIBUTORS, AND IS FOR INFORMATIONAL PURPOSES ONLY. The information contained in this document represents the current view of Hospitality Data Systems Inc. on the issues discussed as of the date of publication. Because Hospitality Data Systems Inc. has no control over the skills of the user, how the information will be used, and must respond to changes in software and market conditions, it should not be interpreted to be a commitment on the part of Hospitality Data Systems Inc.

THE INFORMATION PROVIDED IN THE HOSPITALITY DATA SYSTEMS INC. KNOWLEDGE BASE IS PROVIDED ‘AS IS’ WITHOUT WARRANTY OF ANY KIND. HOSPITALITY DATA SYSTEMS INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL HOSPITALITY DATA SYSTEMS INC., OR IT’S SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF HOSPITALITY DATA SYSTEMS INC., OR IT’S SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

The user assumes the entire risk as to the accuracy and the use of this document. This document may be copied and distributed subject to the following conditions:

1. All text must be copied without modification and all pages must be included.
2. All copies must contain this notice, Hospitality Data Systems Inc. copyright notice, and any other notices provided therein.
3. This document may not be distributed for profit.

Copyright © Hospitality Data Systems Inc. All Rights Reserved
Last date revised - December 15, 2003