Skip to main content
Skip table of contents

20. What information can be queried in the Audit Database?

The Audit database is only active if you are licensed for the AUDIT module and your job/route has "Update Audit Database' set.

As of 4.0.844 It contains 3 tables (Note: the Jobtype_Statistics table is no longer used/written to)

  • [Completed_Work] with the following columns in it:

    • ID (AutoNumber)

    • Date_Time (DateTime)

    • Module_Type (Text)

    • Job_Type (Text)

    • Other_Destination (Text)

    • Input_Filename (Text)

    • Input_Directory (Text)

    • Output_Filename (Text)

    • Output_Directory (Text)

    • Output_Email_Address (Text)

    • Output_FtpServer_Address (Text)

    • Output_File_Format (Text)

    • Output_File_Size (Number)

    • Number_Of_Pages (Number)

    • Elapsed_Time (Number)

    • Routing_Rulename (Text)

    • Processed_By (Text)

    • KFI_Index_File (Text)

    • KFI_Index_File2 (Text)

    • Key_Strokes (Number)

    • Workstation_Name (Text)

    • Operator Name (Text)

    • Zone_Errors (Number)

    • Scanner_Settings (Text)

    • Enhancement_Settings (Text)

  • [Current_Work] with the following columns in it:

    • ID (AutoNumber)

    • Job_Type (Text)

    • Module_Type (Text)

    • Job_Type (Text)

    • Workstation_Name (Text)

    • Operator_Name (Text)

    • Date_Time (DateTime)

  • [Deleted_Work] with the following columns in it:

    • ID (AutoNumber)

    • Job_Type (Text)

    • Module_Type (Text)

    • Job_Type (Text)

    • Workstation_Name (Text)

    • Operator_Name (Text)

    • Date_Time (DateTime)

When Ezescan is installed the default Admin-Options form, Audit database settings are set to use a local copy of the Ezescan_Audit MS Access database. 

If you want to use a centralised Audit Database with several Ezescan workstations you could simply place the Ezescan_Audit MS Access database file (Ezescan_Audit.mdb) onto a network shared drive, and then configure each of the PC's Admin->Options, Audit tab settings to use that network shared database file.  This is only recommend for low volume usage, with a small number of Ezescan PC's.

If there a large number of Ezescan PC's then a better option, would be to create an Audit database on a networked MS SQL Server and then configure the EzeScan Audit Database ODBC connection to use that database rather than the local or network shared EzeScan_Audit.mdb file. FAQ #55 provides information on how to do this.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.