Technical Documents

STARTUP.DAT:
While not a .txt file, StartUp.DAT should still be considered a technical document. Beginning on 08/09/21 with Version 8.00.93, each time the Keystroke program is loaded the Startup Switches used are written to the file StartUp.DAT in the data folder. This file can then be used to help when setting up the Keystroke program on a new system if necessary. Older entries in this file will be dropped off once the file reaches about 32K in size.

AddField.txt:
Copies one file to another file while adding new text (FieldInfo) to the end of each record. Can be used to add one or more fields to a file that may be required in order to import the information into another program.

ARPayOff.txt:
Pays off all open items (except Credit Memos) for all customers. It is the same as the Automatic Payments function in the Accounts Receivable module with Pay Off set to All and no filter set.

ASC2INI.txt:
Converts a Quote/Comma delimited text file to an INI text file format. Once the file is converted to INI format, a batch file or other custom program may be run to further manipulate or otherwise utilize the file. An example use of the ASC2INI.EXE program would be to convert data to the file format required for ImpTRN.exe or ImpPOR.EXE (other utility programs available for Keystroke). In other words, an Quote/Comma delimited file obtained from an inventory Vendor or E-commerce host can be converted to an INI file and then be imported into Keystroke as a Sale or Purchase transaction.

BttnEdtr.txt:
The Keystroke Button Editor is used to edit the settings for the selected button. It displays the button's settings as well as a sample of the button (in the upper right corner of the editor). The "Ok" and "Cancel" buttons are used to close the editor. The "Ok" button saves any changes and the "Cancel" button abandons any changes. The "Advanced" button is used to load additional, less frequently edited advanced Button properties which can be more difficult to correctly edit.

ChgNums.txt:
Packs and renumbers either the Inventory or Customer Database. It also updates old transactions to reflect the new Customer and Inventory Numbers. The numbers are assigned based on the starting number specified and the location of the record within the database file. Note that the physical location of the records within the file can be manipulated before hand through the use of the Importer Module.

ChkNum.txt:
Checks to make sure that the two specified Keystroke Database files (Inventory, Customer, Vendor, Clerk) files have the same Next Number stored in them. The program syntax is:
ChkNum FILE1 FILE2 [UPDATE]
If the Next Number in each file is different, the program returns an error in the file ChkNum.err (the file will be erased if no error). The program writes the results to the file ChkNum.log. If the Optional UPDATE parameter is used, the program copies the numbers from FILE1 to FILE2, does not generate Error Level 1 or 2, and still prints the comparison of the original two numbers in the log file.

ChkStamp.txt:
Checks to make sure all the specified files belong to the same data set by reading the date/time stamp written to the file by the STAMP program. One (and only one) file name must be specified. The file name can include wild cards to represent several names (just as the DOS DIR function can do). The results are written to the file ChkStamp.log. If there is an error it will return the ErrorLevel on the first line of the file ChkStamp.err as "ERRORLEVEL=#" (where # is the error level number). ErrorLevel=1 is reported if any files don't match. ErrorLevel=2 is reported if any files are not valid.

Colors.txt:
The Colors.txt file is used by the Digital Sign Controller to define the RGB color settings for the color labels (i.e. DarkGreen, LightGoldenRodYellowWhite, etc.) referred to in the Digital Sign Controller settings files (i.e. DigitalSignControllerSettings.XML, SampleContent.XML, etc.).

ContPric.txt:
Contract Pricing is a standalone application created for use with Keystroke for the entry and editing of contract pricing. The program charges the Customer's contracted price (if it is not expired) regardless of other pricing or price table discounts that may be available.

ConvLBL.txt:
Converts old label files (.LBL) to the new format (.LL*#####.KSR). The old file must be in the FORMS\ folder and the new file is created in the REPORTS\ folder. The *##### is replaced by the next available number. The syntax is: CONVLBL OldLabel. Do not place a path or file extension on the OldLabel filename, the program does it automatically (Forms\OLDLABEL.LBL).

ConvPTG.txt:
Converts old price tag files (.PTG) to the new format (*.TAG). The old file must be in the FORMS\ folder and the new file is created in the Reports\ folder. The syntax is: CONVPTG OldPriceTag. Do not place a path or file extension on the OldPriceTag filename, the program does it automatically (Forms\OLDPRICETAG.PTG).

CopyCLK.txt:
Copies the time clock information from the file KSCLK.TMP to the file KSCLK.DAT. The times are copied only if they are newer than the present times.

CopyNum.txt:
Copies the second record (FileData which holds the next number values) from the transaction file EXTRACT.MRG to the customer data file KSCST.DAT.

CuponChk.txt:
Prints a coupon form when a certain items are present on a Keystroke Transaction. The program reads a list of line items from a Keystroke Transaction and checks those items against a list of Inventory items in a Check File. If a Line Item on the transaction is present in the Check File then a coupon will be printed. Line Item information can be printed on the coupon by using tokens. If the word DUPLICATE is present on the first line of the Item File then the program will not process the data. This is to prevent the printing of coupons if the invoice is edited and re-printed or to prevent the printing of multiple coupons from the same transaction. The program uses one command line switch, INIFILE=, followed by the location to find the INI file containing the program settings.

CustDate.txt:
Reset every customer's Oldest Open Invoice Date to the current Date/Time.

DashBrd.txt:
This document describes how to control the display of the Keystroke Dashboard and the Dashboard's display tiles.

DateName.txt:
Changes the name of a file to a file name representing the current date. The syntax is: DateName FileName1 FileName2 [FORMAT=MMDDYY].

DBLists.txt:
Used to edit the Valid Entries List Files that are available for each database field in Keystroke. Keystroke uses these lists (if they exist) to validate entries made into each field as well as to provide the clerk with the ability to look up an entry on the list by pressing [Ins] while in the database field.

DBNames.txt:
This document contains a list of all the fields used on Reports as well as the Export and Import functions.

DelTrans.txt:
WARNING: This utility should be used ONLY with the assistance of a Keystroke Technical Support Specialist AFTER a backup of data files has been completed. It is used to remove sales and purchase transactions that match the parameters entered on the command line. Both a Start Date (START=) and Ending Date (END=) must be specified. Changes are recorded in the DelTrans.log file in the Data Folder.

DelUtil.txt:
WARNING: This utility should be used ONLY with the assistance of a Keystroke Technical Support Specialist AFTER a backup of data files has been completed. It is used to run special data file maintenance routines that are not available from within in the Keystroke program itself. These routines include: deleting and then updating orphaned/duplicate payments and Back Orders/Open Orders with their associated inventory quantities, updating Credit Memos, and updating Account Receivable balances.

DetBox.txt:
Describes the layout of the TRNDET#.DAT, PORDET#.DAT and VARDET#.DAT files which control the Detail Box display setings in the Sales Manager, Purchase Manager and Variance Modules.

ExpSum.txt:
Copies one or more Summary Data files to a file in an ASCII Delimited format. The program creates files with the same names as the original file but with the extension of .txt.

Extract.txt:
One of the Keystroke MultiStore utilities used to manage sales and inventory in multiple store locations and/or warehouses. It extracts transactions into the file Extract.MRG so they can be merged into a different set of data files with the StoreMrg utility. Extract supports most of the standard Keystroke command line switches as well as some special switches. These switches can also be specified in the file EXTRACT.DAT. Please contact your Authorized Keystroke Point Of Sale Dealer for details about setting up MultiStore utilities.

Filters.txt:
Contains a list of the Report and Export filter field numbers used in Keystroke and by some Keystroke stand-alone programs.

Fix2INI.txt:
Converts an ASCII fixed length file to an ASCII file in the INI file format. Once the file is converted to an INI format, a batch file or other custom program may be run to further manipulate or otherwise utilize the file. An example use of the FixINI.EXE program would be to convert data to the file format required for ImpTRN.EXE or ImpPOR.EXE. In other words, a fixed length file obtained from an inventory vendor or E-Commerce host could be converted and then be imported into Keystroke as a Sales or Purchases transaction.

Form2lbl.txt:
Enables the placement of information available only in the header section of a form to be placed within each line item (the body section). It does this by reading in a text file which contains Token definitions in the header section and then replacing the Tokens found in the body section with the value of the token. The text file name must have the extension .FRM. The program will search for any file with the extension .FRM and then read it in, replace the tokens, and then send it out to the printer. A token is defined by placing a single character between two ampersands followed by the value of the token.

FormQty.txt:
Reformat a number in a text file to have a fixed number of decimal points. It is intended to be used when printing forms out of the Keystroke program. The text file name must have the extension .FRM. The program will search for any file with the extension .FRM and then read it in, replace the Qty token with a reformated number that has the specified number of decimal points, and then send it out to the printer. A Qty Token is defined by placing a the three characters "&Q#" (where # is replace by the number of decimal points) in from of the number and a single character "&" after it:

&Q2 1& is changed to 1.00
&Q2 1.2& is changed to 1.20
&Q2 99.999& is changed to 100.00

Note that the token characters are thrown away. So when creating a form, don't count the spaces taken up by the &Q# or last &.

GetMail.txt:
Read entries in the Inbox of the specified MAPI server. Entries that match the specified parameters will have their attachments saved to the specified path and will then be deleted. This program is designed to be used in e-Commerce applications as well as Multi-Store polling procedures. The settings are controlled through the file GETMAIL.INI. The only command line switch supported is INIFILE= to use a different file than GETMAIL.INI.

GLLink.txt:
Creates journal entries in the specified file and format as defined by the Setup Parameters in the Keystroke Accounting Link module.

Header.txt:
WARNING: This utility should be used ONLY with the assistance of a Keystroke Technical Support Specialist AFTER a backup of data files has been completed. It is used to read and edit transaction file link information.

HideDel.txt:
Changes the flag on deleted database records still available for recall to be hidden records instead of deleted records. Works for both the Inventory and Customer databases. The database needs to be packed after this utility is run.

Imp.txt:
Import data from a source file as defined by the specified Import Setup File Parameters in the Keystroke Data Importer module.

ImpAltIC:
Imports Alternate Inventory Codes into Keystroke (also Alternate Customer and Vendor Codes). The source file to be imported must be in ASCII delimited format where the first field is the new Alternate Code and the second field identifies the existing database record in Keystroke.

ImpLines.txt:
Provides additional instructions on how to use the Import Transaction function under the Special Menu in the Keystroke Sales Manager. This function can either be run manually by selecting it from the Special menu, or automatically by setting the Dataport Import Parameters. This function works the same as ImpTRN.EXE with a few exceptions. The file format is the same with just a few exceptions. The ImpTRN.txt should be read before proceeding with this document.

ImportAR.txt:
Imports Accounts Receivables Customer Balances into Keystroke by creating a Balance Forward invoice for the balances contained in the ASCII delimited file CustBal.txt. The first field in this file is the Customer Code (unless changed by a switch), the second field is the total balance, any other fields represent the balance for previous periods. Note that the balances from previous periods are optional and the amount posted to the current period is the total minus these other fields' values.

ImpPOR.txt:
Reads an ASCII source file containing transaction information (in an INI file format) and creates new purchase transactions from the information provided. Each transaction must start with the line **START TRANSACTION and end with the line **END TRANSACTION. Each Line Item must start with the line **START LINE ITEM and end with the line **END LINE ITEM. These tags allows multiple transactions to be imported from the same source file.

Each piece of information is preceded by the field's title followed by an equal sign. Print a transaction to file using the form file IMPPOR.POR to see a complete list of all the fields supported and an example of how the file should look. (Fields marked by '** are supported but should be avoided when possible). Also see ORDERS.POR for a stripped down example. Note that the order of the fields does not matter in most cases. However, it does matter when identifying vendors and inventory items by fields other than the vendor number and stock number. If the number field is not imported, then the first indexed field used in the file will be used to look up the database record. Also, the field used to identify the vendor/inventory record must be the first field in the source file for each record (vendor or inventory item) since when the record is looked up, all fields are updated based on that record (i.e., if some of the fields from the transaction are read in and then the record is looked up, the transaction fields already read in are replaced with the information from the database record).

Any setting made by the imported transaction is retained whenever possible (e.g. Tax Amount, Transaction Number, etc.). Any information not included in the source file uses default values (just as if a new transaction was being entered by hand).

ImpROA.txt:
Imports Received On Account payments by creating an ROA payment for each payment found in the source file being imported and applies the payment to the specified invoices (if any). If the payment amount and amounts applied do not match, then the ROA payment generates a Credit Memo.

ImpTRN.txt:
Reads an ASCII source file containing transaction information (in an INI file format) and creates new sales transactions from the information provided. Each transaction must start with the line **START TRANSACTION and end with the line **END TRANSACTION. Each Line Item must start with the line **START LINE ITEM and end with the line **END LINE ITEM. These tags allows multiple transactions to be imported from the same source file.

Each piece of information is preceeded by the field's title followed by an equal sign. Print a transaction to file use the form file IMPTRN.NVC to see a complete list of fields supported and an example of how the file should look. (Fields marked by '** are supported but should be avoided when possible). Also see ORDERS.NVC for a stripped down example. Note that the order of the fields does not matter in most cases. However, it does matter when identifying customers and inventory items by fields other than the customer number and stock number. If the number field is not imported, then the first indexed field used in the file will be used to look up the database record. Also, the field used to identify the customer/inventory record must be the first field in the source file for each record (customer or inventory item) since when the record is looked up, all fields are updated based on that record (i.e., if some of the fields from the transaction are read in and then the record is looked up, the transaction fields already read in are replaced with the information from the database record).

Any setting made by the imported transaction is retained whenever possible (e.g. Tax Amount, Transaction Number, etc.). Any information not included in the source file uses default values (just as if a new transaction was being entered by hand).

INIMerge.txt:
Merges information from a data file into a master source file and then sends the output to a specified device (file or printer). The data file must be in the INI format. The Master Source file contains Tokens that match the field names in the data file. The tokens are in the format &FieldName=&. These tokens are replaced with the matching data from the data file. The program repeats the use of the master file for each series of data in the data file (e.g. line items).

InvLink.txt:
Reads the current inventory data file and then writes QOH information to a file named KSIL#.DAT were # is the store number as defined in the Configuration Module. The KSIL file can then be read from an inventory record by pressing [Shift+F5] to display the QOH for all the stores for which a KSIL#.DAT file is available.

Keystroke.txt:
Contains a list of the more commonly used standard and special Keystroke Start Up Switches for Keystroke.exe.

KS2QB.txt:
Exports Keystroke General Journal information to a file called journal.rpt located in the Keystroke installation folder and then prompts to import the file contents into QuickBooks. Access to the Company File in QuickBooks is required.

KSBackup.txt:
Uses ZIP.EXE from Info-ZIP software (Zip, UnZip and related utilities) which is freely distributed under the Info-ZIP license and can be obtained as source code or executables from various anonymous-ftp sites, including ftp://ftp.info-zip.org/pub/infozip (or view www.Info-ZIP.org or the files in the Keystroke\Doc\Info-Zip folder). Three files are created in the specified destination: YYMMDD.ZIP, YYMMDD.LST, and LASTBACK.TXT. YYMMDD represents the date of the backup (a dash followed by a character may be added if a backup already exists for the current date). The .ZIP file is the backup and the .LST file is a list of all the files that were backed up. LastBack.txt holds information about the last backup performed.

KSExport.txt:
Describes how to run the command line version of the Export function found in the Configuration Manager, including the supported special switches.

KSR.txt:
Runs a Report Cue from the Command prompt and can identify the specific Cue by its Cue Name or its Cue ID Number.

KSRestor.txt:
Restore all files store in a backup made with KSBackup.EXE to the current folder structure. The LastBack.txt file is checked to find the name of the last backup file and a prompt is displayed to restore it. UNZIP is used to restore the files. A prompt for a password is displayed. If no password was used when the backup was created, just press [Enter] to continue.

MapFile.txt:
Copies an ASCII delimited file to another file while rearranging the order of the fields. The field order is determined by the specified Mapping File. The Mapping File is a simple text file with one number on each line. The line number is the field to copy to and the number on the line is the field to copy from. If no Mapping File is specified, then the fields are copied as they are (the purpose of this is to change the delimiter being used.)

Field numbers in the Mapping File can be repeated or skipped. Putting the letter N after the field number marks it as numeric. When using a Quote/Comma delimiter, these numeric fields are not be enclosed in quotes. A field number of 0 prints whatever else is on the line to the file. If there isn't anything following the 0, then a blank field is printed using the specified delimiter. If there is something following the 0, then that text is printed without adding any additional delimiters. If delimiters are desired, they must be supplied with the specified text.

The syntax is: MapFile FileName1 FileName2 [MapFile] [Delimiter=1].

NVC2LBL.txt:
Reformat and print transaction information to a Keystroke printer or file. Uses token values to replace information and format the transaction information.

Source File: NVC2LBL reads in the transaction information from the designated Source File and replaces token values in the Mask File with the corresponding information from the Source File. The Source File is a basic text file that contains a list of transaction information to be placed on the formatted form. Each piece of information in the Source File is referenced by the line number that contains the data. For Example: The following Source File has 3 lines of Line Item data per transaction and contains 2 transactions.

01/01/01
445566
2.50
01/01/01
111222333
100.00

In the above source file the date is referenced as Line Number 1, Product Code as Line Number 2, and the Price as Line Number 3 for each transaction.

Mask File: The Mask File should be formatted, including print codes, to correctly print the desired output without the replaced information. If a Condensed print type is needed then the appropriate Print Codes for the printer to print condensed type should be contained in the Mask File. The easiest way to create a Mask File with the correct print codes is to print a Mask File to file from Keystroke using the correct printer driver. The Mask File should contain the token values where the corresponding data from the Source File is to be placed. The Token format is as follows:

&# LINE NUMBER&, where the # is the line number of the desired data from the Source File. Tokens must be all upper case.

PrintSal.txt:
Prints a range of sales transactions to the specified printer in the specified format. It is typically used to print a batch of sales transactions after they have been entered into the system but not yet printed (e.g. after using RecMerge to import a series of Recurring Invoices or after using ImpTRN to import new Sales Orders from an E-Commerce system). The series to be printed is defined by the type of transaction (default is Sales Invoice) and the date/time range (default is last Midnight through the current Date/Time). Up to two filters (same filter options as those found in the Sales Transactions report) can also be used to further define the batch. The default form/printer used is determined by the Print Button #1, or the print button number to use may be specified.

Prod.txt:
Runs the Production Module's Auto Produce function which is used to automatically produce all items that need to be produced based on their current Quantity On Hand (plus Quantity On Order) and the Minimum Quantity levels. When the Auto Produce function is selected, the Production Templates are searched for items that need to be produced. When a Template is located for an item where the sum of its Quantity On Hand and Quantity On Order is less than its Minimum Quantity, a Production run is generated. Items will be automatically produced only if the Auto Produce parameter is enabled on the Production Template for the item.

RecChrg.txt:
Merges recurring transactions by copying them from one specified transaction type (e.g. FROM=REC) to another specified transaction type (e.g. TO=NVC). As the transactions are copied, the payments are also copied and any that need to be processed (have an Authorization Method) do get processed. Any payment that fails to be processed causes the transaction to be copied to alternate transaction type (e.g. ALT=HOLD). The transaction type tags are defined by the Sales Transaction Type's Abreviation which is set in Configuration Manager, under Settings, Sales Transactions, on the Sales Transaction Type screen, Abbreviation field.

Even though RecChrg.exe exists as a standalone program, it really is just a shell that calls "Keystroke.exe /GRecChrg" plus any command line parameters entered with it. The /GRecChrg causes Keystroke to jump to the Sales Manager module and run RecCharge function built into it. This function emulates the steps a clerk would perform manually to copy the transaction by using the Transaction Copy function and then save the transaction. However, this function goes through all the transactions sequentially without any extra input from the clerk. The only required Start Up Switch is the ID= switch which is used to identify which Process Recurring Charge Settings to use (multiple settings may be avaialble).

RecMrg.txt:
This program can be used for two purposes. It can be used for NETWORK RECOVERY (Recovery Merge) or it can be used to process RECURRING TRANSACTIONS (Recurring Merge - without credit card authorization processing). To merge transactions with credit card payments that need to be authorized using the Keystroke Payment Module (KeyPay.exe), use RecChrg.exe (see RecChrg.txt right above this section). For either purpose, Sales Transactions are merged from the file KSTR0001.REC into the Sales Invoices transaction type. The file KSTR0001.REC is a transaction file that is a copy of a standard sales transaction file such as KSTR0001.DAT.

RECURRING TRANSACTIONS: Run without the use of any switches, the transactions are dated and numbered as though they are being entered manually today, using the Next Number and today's date. This is mainly used to bring in monthly club membership dues (but RecChrg.exe is better).

NETWORK RECOVERY: It can also be used as Recovery Merge by using the /ADD switch to retain the existing transaction numbers and dates.

The Merge= startup switch may be used to merge one Transaction Type into another (Merge="REC TO NVC").

RemDupes.txt:
WARNING: This utility should be used ONLY with the assistance of a Keystroke Technical Support Specialist AFTER a backup of data files has been completed. It is used to delete duplicate Sales Transactions, Purchase Transactions, ROA Payments, and Time Clock entries. It is most commonly used when the same set of transaction data was accidently merged in more than once (either through the StoreMrg or RecMrg programs). The transactions must be exact duplicates (which can really only happen through a merge function). If the same transaction was simply entered twice, they would not be exact duplicates since the Time Stamps would be different. A log file is created in the data folder (RemDupes.log) and records the date/time at which the program was run and the transaction records that were deleted.

ReplCost.txt:
Used to adjust the cost stored with Sales Invoices that have already been entered. The program replaces the cost on the Sales Invoice Line Items over the specified date range for a particular stock number, department, or all inventory items with the current last or average cost that is stored in Keystroke. It can also be used to calculate a margin based off of the price that the item was sold it for. Currently all stock numbers must be less than 1,000,000 or the program will fail. The program's parameters are controlled using the Replace Cost program interface screen displayed when ReplCost.EXE is run.

Reports.txt:
A custom reporting program for Multi-Store customers to enable reports to be run from up to 20 stores' data folders to produce inventory, payments, and analysis reports.

Scrpt.txt:
Documents the format of the ASCII file used to Export/Import Scripts. The file is an ASCII Quote/Comma delimited file where each record is on a single line. The first field of each record identifies its type. There are 3 types of records; Main ("M"), Script ("S"), and Item List ("I"). The Main record identifies the inventory item to which the Script is attached. The Script records (there can be 0 to 30 of these following each Main record) contain the Script settings for each Script line. The Item List (there can be 0 to 1 of these following each Script record) lists the individual inventory items that can be selected from the Script.

SendKM.txt:
Sends an email to the specified receipient(s) by connecting to the KeyMail program and providing it with the required information. KeyMail then does the rest of the work to send the email through the specified email server. KeyMail must be set up and running correctly before this program can be used. The program can be used in a wide variety of ways (e.g. send information to an eCommerce site, send Reports or Invoices that have been printed to a file, or used in specific integrations like Multi-Store polling procedures). The methods and the formats used are similar to the use of a printer set up inside Keystroke with its port set to the MAIL: port. In fact, SendKM is a stand-alone version of the same code.

SplitTrn.txt:
Used to force Keystroke to begin saving transactions to a new transaction file. Marks the latest transaction file with a new ending date and then creates a new transaction file that starts on that same date. When run, the Split Keystroke Transaction File interface screen is displayed prompting for the required information. To run as command line utility, add the switch /NOP for No Pause (along with the other switches necessary to provide the required information). Everytime SplitTrn is run it writes a log entry to either the SplitTrn.LOG file in the Data folder if the split was done, or to the SplitTrn.ERR file in the Program folder if the split was not able to be completed.

Stamp.txt:
Stamps the specified files with the current Date/Time by writing a serialized representation of the Date/Time that the Stamp program was run to the first record of each file. One (and only one) file name must be specified. The file name can include wild cards to represent several names (just as the DOS DIR function can do). The specific size of each file must be at least 2048 bytes and be must be divisible by 128 (all Keystroke Database and Transaction files meet these parameters). This stamp can then be used by the ChkStamp program to make sure all the files are from the same data set.

StampVer.txt:
StampVer is used to change the Version Number stamp in data files so they can be used by an older version or can be set to not convert again (data format of the data files must be compatible). It supports just three command line switches. Version= is set to the New Version to stamp the data set with. Build= is set to the Build Number to stamp the data set with. /D = is set to the Data Folder (if needed).

StoreMrg.txt:
StoreMrg (Store Merge) is one of the Keystroke MultiStore utilities used to manage sales and inventory in multiple store locations and/or warehouses. StoreMrg is used to merge transactions from the merge file EXTRACT.MRG (created by the Extract utility) into a different set of data files. StoreMrg supports most of the standard Keystroke command line switches as well as some special switches. These switches can also be specified in the file STOREMRG.DAT. Please contact your Authorized Keystroke Point Of Sale Dealer for details about setting up MultiStore utilities.

StrUpdte.txt:
Runs the Update Inventory function from the Store-Link module using the settings from the Store Information options, the Inventory Update Parameters, and the Inventory Consolidation Parameters. StrUpdte can also run just the Consolidate Inventory function by running StrUpdte with the command line switch "ConsolidateOnly=1" (don't run Update Inventory, run just Consolidate Inventory even if the Run with Inventory Update - Inventory Consolidation Parameter is disabled).

Summary.txt:
Runs the Summarize History function from the Database Manager but uses command line switches instead of the settings from the Summarize History screen. The current transaction history for the specified date range is read and the information is written to a file named dpyymmdd.DAT located in the Data\Summary folder. The "d" in the file name represents the Database (I=Inventory, C=Customer, V=Vendor, K=Clerk). The "p" in the file name repesents the Period (D=Daily, W=Weekly, M=Monthly). The "yymmdd" in the file name represents the starting date for the Period. The Summary information is viewed in Keystroke by pressing [Ctrl+F5]. If no period is specified, every period file for the specified date range is created. If a week or month ends within the date range, a file for that week/month is created. If the Period= parameter is used, only files for that type of period are created. If the Database= parameter is used, only files for that database are created. If no date range is specified, file are created beginning with the previous day, going backwards until a summary file that already exists is reached (or back 7 days for daily files, 5 weeks for weekly files, and 1 year for monthly files).

Toolbars.txt:
Keystroke's TouchScreen utilizes a variety of on-screen buttons grouped in boxes called Toolbars that can be used to quickly issue very simple to very complex commands with a single mouse click or the touch of a finger. Each button within a Toolbar (and the Toolbar itself) is configurable in its look, size, and the actions it performs.

Toolbar Data files contain the settings that control the layout, appearance, and function of the Toolbars and the buttons located within them. The Toolbar Data files are text based and use a simple XML format allowing them to be edited with any text editor or XML editor, as well as with the TouchScreen Editor and Button Editor built into Keystroke.

Toolbar Data files are stored in the Toolbars\ folder beneath the Data folder. The name of the default main Toolbar Data file is TB.DAT. The Toolbars for a standard Keystroke installation are controlled by the file C:\Keystroke\Data\Toolbars\TB.DAT.

The name of the main Toolbars Data file can be changed by using the "ToolBarsFile=" INI file setting or Start Up Switch to specify a different file name. The file's extension (usually .DAT) must be specified. The path to the file's folder location cannot be changed (the file must be located in the Toolbars\ folder below the Data folder).

The Keystroke TouchScreen is displayed by reading the settings from the main Toolbar Data file. The file normally includes settings for multiple Toolbars, each defined by a [ToolBar Name=] element. However, individual ToolBar settings can also be called from other Toolbar Data files as well. The [ToolBar FileName=] element is used to read an individual ToolBar's settings stored in its own separate file and then called from the main ToolBar Data file. For example, a Toolbar call "PetFood" could be created and saved in its own file (e.g. "Toolbars\PETFOOD.DAT"). Then by adding the element [Toolbar FileName="PetFood"] to the main ToolBar file, this file (and the PetFood Toolbar settings stored in it) is loaded as though its settings were included in the main file. This allows specialized ToolBars to be installed and updated at multiple locations without the need to change the main ToolBar Data file each time.

UDPrice.txt:
Used to update the price fields for inventory items using a specified Price Table (and its corresponding Price Formulas). It works the same as the Search & Update Price function in the Database Manager except it uses Filters instead of the Search screen to specify the items to update. To update more then one price field or to use different tables/dates with different items, set up a batch file to run this program multiple times, each time updating a different field and/or set of items. To prevent any item from being updated by Price Table Formulas set its Price Code field to Blank. Items with no Price Code cannot be updated via price formulas.

UPCCost.txt:
Used to update the Last and Average Cost of items that have a Parent/Child relationship. Updates the Last Cost field of each Child to match that of the Parent (taking into account the Order Multiplier). The Average Cost of the items is updated by first recalculating the Average Cost of the parent after rolling all the (QOH+QtyOnLayaway+QtyAllocatd) and Avg.Cost from its children up into it and then resetting the Avg Cost of each Child to match. Filters may be used to specify the items to update. The Filters apply to only the main parent item (an item that has children put no parent). Children of a Parent that matches the filter will be updated even if the Child itself does not match the filter.

Keystroke Point of Sale Help

Technical Documents