Table Of Contents Compact Database

Logs


Overview

Several logs are available for displayed in the same general format under the Tools | View Logs menu. The logs available include Data Transfer Query (shown below), Scale History Log, Tare History Log, Tickets Table, Transaction Log and Transmission History.

 

.Generate/LOG DATA TRANSFER2.gif

Toolbar

The toolbar is similar for all logs although not all buttons are applicable to all logs. For example, the Purge button is disabled (grayed out) on the Data Transfer Log, and the Retransmit button is only enabled for the Transmission History log.

Generate/LOG TOOLBAR2.gif

Close

Closes the log display.

Reset

Sets the column layout, position and widths to their default values.

Purge

Removes records prior to (older than) and including the currently selected record. This feature is used to remove old or unnecessary data from the database.

Note:      The purge function is based on date or key sequence and not the current sort order. If you have changed the layout sort order, the records deleted will not necessary be those visibly above or below your selected record.

Note:      The purge function is disabled when viewing the Data Transfer Query log. It is enabled for all other logs.

Note:      The purge function will never delete the Default record identified by the Sys_Default field equal to one (1).

Click on the most recent record you want to delete to then click the Purge button. You will be prompted to verify your request. If you respond positively, all records up to and including your selected record will be permanently deleted.

IMPORTANT:      Purging is a permanent operation and can not be reversed. We strongly recommend backing up your data before proceeding.

Retransmit

Retransmits the selected batch of records.

Note:      Retransmit is only enabled while viewing the the Transmission history log. It does not apply to any other log an is disabled while viewing other logs.

Layout

You can sort records by different columns and change the column positions and widths of all the logs.

Sort

To sort a log by a different column, click on the column title that you want the records sorted by.

Column Width

To change the width of a column, move the mouse cursor between two column titles. The cursor will change to a column sizer icon.

Generate/log column width2.gif

Press and hold down the left mouse button as you drag the column sizer to increase or decrease the column size. When the column is properly sized, release the left mouse button.

Column Position

To change column positions, press and hold the left mouse button down on the title of the column you want to move. Drag the column left or right to the new position and release the left mouse button.

Reset

Click the Reset button on the toolbar to reset the column layout to their defaults.

Fields

Following is some general information about fields that may be helpful.

Key Fields

Most every table and log in EZScale has a Key field. The Key field is used by the system to establish relationships between tables in the database. Key fields are internally and automatically generated and can not edited by the user. The key fields have no specific meaning that you need to consider when viewing logs except that they do give you an idea of the natural order in which records where created and will be be purged.

True/False Fields

Fields that represent True/False or Yes/No type options, are stored in the database as numbers where zero (0) means False and minus one (-1) means True. So, if you see a column of zeros (0) and minus ones (-1), you can interpret the numbers accordingly.

Inactive Fields

Inactive fields are a True/False type field as described above and indicate the record status. For most of the logs, this field has no

Sys_Default

The Sys_Default field is another internally managed field by EZScale. The Sys_Default field is not editable or of specific value to the end user except that if the Sys_Default field equals one (1), that represents the Default record and will be ignored during a purge.

Data Transfer Query

The Data Transfer Query shows all the fields available and associated with every ticket produced during the Ticketing process that hasn't yet been purged from the system. This query is a superset of all the data in the database that can be associated with the Tickets Table. In other words, you only identify a truck during the ticketing processing. But once we know the truck, we can look up related information about the truck. Likewise for job, purchase order, etc. The data transfer query shows all the related information.

Scale History Log

The Scale History Log shows activity across the scale above a trigger weight regardless of whether or not a ticket was produced. This can be very helpful, for management auditing and security.

Note:      Scale activity is not recorded unless you enable Log Scale Activity under Tools | Options | Event Logs.

When you turn scale activity tracking, you also define a Scale Trigger Wt. under Tools | Options | Event Logs indicating that something is on the scale heavy enough that you want to know about it. Scale activity is ignored below this weight. When the load on the scale reaches the trigger weight, a scale event initiated and the following fields are recorded. The event continues until the load drops back down below the trigger weight.

Generate/do-it2.gif    OnDateTime is the date and time that the scale load rose above the trigger weight.

Generate/do-it2.gif    LowStableWt is the lowest stable weight observed before the load dropped back down below the trigger value. If the scale never stabilizes, this value will be zero.

Generate/do-it2.gif    HighStableWt is the highest stable weight observed before the load dropped back down below the trigger value. If the scale never stabilizes, this value will be zero. If the scale only stabilizes once during the event, the LowStableWt and HightStableWt will be the same.

Generate/do-it2.gif    PeakWt is the highest weight observed regardless of stability.

Generate/do-it2.gif    OffDateTime is the date and time that the scale load dropped back down below the trigger weight.

Generate/do-it2.gif    UserKey is the key of the user logged on when the event occurred. You can lookup the specific user under Maintain | Users. Click the Edit button and look for the Key field in the right column of the Edit list.

Tare History Log

The Tare History Log shows all Tare activity. This can be very helpful, for management auditing and security.

Note:      Tare activity is not recorded unless you enable Log Scale Activity under Tools | Options | Event Logs.

Generate/do-it2.gif    TruckKey is the key of the truck or container that was tared. You can lookup the specific user under Maintain | Trucks. Click the Edit button and look for the Key field in the right column of the Edit list.

Generate/do-it2.gif    DateTime is the date and time the truck was tared.

Generate/do-it2.gif    TareWt is the tare weight recorded.

Generate/do-it2.gif    LoadedTare is a True/False field indicating whether or not Loaded Tare was checked during the Tare operation.

Generate/do-it2.gif    AutoTare is a True/False field indicating whether the weight was captured automatically from the scale or entered manually.

Tickets Table

The Tickets Table shows the raw tickets table data for every ticket produced during the Ticketing process that hasn't yet been purged from the database. This is similar to the Data Transfer Query, except that the tickets table only shows the internally stored key values and does not show other fields from the related tables.

If you know a key value, you can lookup specific information by going to the appropriate table under the Maintain menu. But generally it is easier to simply look at the Data Transfer Query log. The Tickets Table is primarily for administrative purposes and for purging old tickets from the database.

Location

The location is typically used to indicate where the ticket was processed and can be included in a Data Transfer. Location is defined under Tools | Options | General tab.

Transaction Log

The Transaction Log shows most all changes to the EZScale database tables including the type of change, who was logged in when the change was made, and when the change was made. This can be very helpful, for management auditing and security.

Note:      Transaction Log activity is not recorded unless you enable Transaction Log events under Tools | Options | Event Logs.

Generate/do-it2.gif    TableName is the internal database table name where the modification was made. The table names will generally correspond very closely with the tables under the Maintain menu.

Generate/do-it2.gif    ID is the user defined ID of the record that was changed. This is the same ID that you select when you click the Edit button to view a list of records for a table.

Generate/do-it2.gif    FieldName is the internal table field name of the specific field that was modified. The field names will generally correspond very closely with the form labels for the associated table.

Generate/do-it2.gif    OriginalValue is the value of the field before it was modified. An entry of <NEW> means that the field belongs to a new record that was just added to the table and did not have an original value.

Generate/do-it2.gif    NewValue is the value of the field after it was modified. An entry of <DELETED> means that the field belongs to a record that has been deleted from the table and has no new value.

Generate/do-it2.gif    DateTime is the date and time that the modification was made.

Generate/do-it2.gif    UserKey is the key of the user logged on when the event occurred. You can lookup the specific user under Maintain | Users. Click the Edit button and look for the Key field in the right column of the Edit list.

Transmission History

The Transmission History lists each batch of records that were transmitted using the Tasks | Transmit Data menu option. The log shows the number of records transmitted and the date of transmission. You can retransmit a batch from this log by selecting the record to retransmit and clicking the Retransmit button in the toolbar.

 

 



Table Of Contents Compact Database