CHECKFIX Utility

Last edited: December 15, 2003 08:07 AM

Checkfix is a utility that rebuilds the stored check index file CHECKS.DAT from the CHK files in the CHECKS directory. It also resets the Check in Use flags.
Installation

The executable should be placed in the TOOLS directory, or at least in a directory in the PATH. Run CHECKFIX from the application directory.

SYNTAX: CHECKFIX {/INIT}  {/AUTO}  {/?}

    * /INIT will initilize the video. Use when not run from Touchnet.
    * /AUTO will skip the user confirmation screen normally displayed upon completion.
    * /? Displays help info.

INSTRUCTIONS:

1. Create a shell in Editnet with the following parameters:

        * Working Directory: [ ]
        * Command Line: [CheckFix ]
        * Lowest Variable: [ 64]
        * Highest Variable: [ 64]

    On Exit:

        * Reset Video
        * X -Store Variables
        * X – Preserve Screen
        * Store Check PLU List
        * Lock Video
        * X – Swap to XMS/EMS

    On Return:

        * Initialize Mouse
        * Get Variables

2. Make a button to call the shell.
Technical

It is known that if a CHK file is corrupt CHECKFIX will generate an error 63 or an error 5 when trying to read the corrupt CHK file. In this situation the CHK file is unrecoverable and will not be able to be read from TOUCHNET either. TOUCHNET will generate an error 5 when trying to retrieve the corrupt CHK file. CHECKFIX will delete the corrupted CHK file and continue with rebuilding the CHECKS.DAT. Any deleted CHK files will be displayed on the screen after the rebuild is complete. CHECKFIX will also create a list of the deleted CHK files in CHECKFIX.ERR located in the directory it was run from. Upon running CHECKFIX again, it will delete CHECKFIX.ERR in order to create a new fresh list.

If CHECKFIX finds an existing CHECKS.BAK file it will delete it. If CHECKFIX finds an existing CHECKS.DAT file it will rename it CHECKS.BAK.
Revisions

8/16/95 Version 1.0

  1. CHECKFIX is a utility designed to rebuild the CHECKS.DAT file located in the CHECKS directory (child of application directory). The program will first copy the existing CHECKS.DAT file to CHECKS.BAK. Then it will read the individual CHK files for necessary information and create a new CHECKS.DAT file.

8/18/95 Version 1.01

  1. Added the ability to CHECKFIX to screen any corrupt CHK files. If encountered CHECKFIX will delete the corrupt CHK file and resume rebuilding the CHECKS.DAT file. Each corrupt or unreadable CHK file that is deleted will be stored in a file called CHECKFIX.ERR located in the directory the executable is running from. CHECKFIX will display the error results on completion of the rebuild.

11/09/95 Version 1.02

  1. Updated the help message. Added the ability to check for proper paths in order to force the user to run from the application directory.

11/22/95 Version 1.03

  1. Fixed a bug in v1.02 relating to checking for proper paths.

08/05/96 Version 2.00

  1. Version 5.xx (TouchPRO) compatibility.

01/10/96 Version 5.01

  1. Changed version time stamp to match the current version of Touchnet.
  2. Added window to display progress and any other necessary information. Will respond to touch or key press. This was done in order to read the output of CheckFix when run from CHOOSE or when run as a shell.
  3. Added print to local printer feature. Will print list of corrupt checks if found to local printer formated for 40 columns when used as a shell from TouchPRO. Will support printers defined as files also.

03/10/97 Version 6.00

  1. Compiled to be compatible with version 6.xx core product. Only change is version checking.

06/18/97 Version 6.01

  1. Fixed a bug that would cause checks to disappear from the CHECK RETRIEVER window. This would happen when a server who’s employee record utilized both first and last names was assigned to the check and then Checkfix was run. The check would still be in the checks folder, but not in the checks.dat index file.

11/12/98 Version 6.02

  1. Added a command line switch (/AUTO) to skip user confirmation normally displayed upon checks.dat rebuild completion.