HLR Section 2
Job Identification Data
CONTENTS
| 2.1 Names & Descriptions 2.2 Heavy Load Application Numbers 2.3 HL Applications Database
| Other Links: | Main Index | Analysis Options | Route Data | Vehicle Data |
2.1 Names & Descriptions
| Job identification data is entered via the Job ID tab on the main Data Entry form as shown below. Name of Company Enter the company/operator's name. This value is essential if the box associated with key job ID data in Options/Default Settings has been ticked. Vehicle Description Enter the vehicle name/description. If you intend loading a vehicle off the database this may be left blank. Route Description Enter the route name/description. If you intend loading a standard route off the database this may be left blank. Although you will also be able to enter a route description via the Route tab, the value entered here will be the one used in all reports. Note, however, that if the description entered on this form differs from the one on the Route tab, HLR will prompt you for the description you would prefer to use in all reports. This is done just prior to the analysis. HL Number Refer to Section 2.2 for a detailed description of this number. A unique number must be provided if you intend saving the job data to the HL Applications database. Application Number Refer to Section 2.2 for a detailed description of this number. Notes & Comments Enter any required notes and comments. An option is available on the Reports form for including these comments in all reports (Summary Report as well as Restricted/All Bridges reports). Save Application to Database This button saves all data for the current HL assessment (or job) to the HL Applications database. Refer also to Section 2.3 for further details regarding the Applications database. Begin New Application This button allows all data for the current application to be cleared and completely new data to be entered. Load the Last Application This button allows all data from the application last processed on your machine to be reloaded.
| 2.1.1 Retrieve Application from Database Click this button if you wish to retrieve an application from the database. If you do, a list of all saved HL Applications will be displayed in a form similar to that shown below. Applications are sorted by date, from the most recently saved Application to the oldest (i.e., in chronologically descending order). Highlight the required application and click Read the HL Application. All data from the selected application will be loaded into the system. Applications can be sorted on any of the fields and in either ascending or descending order simply by clicking the required column title once or twice (multiple clicks act as a toggle). Refer to Clause 2.1.2 below if you want to delete one or more HL Applications from the database. Note that reports and log file associated with the application are not loaded into the system - you will have to re-run the analysis and regenerate them. The only exception is the Summary Report which is saved to the ..\Database\Reports folder (refer also to Section 7.2 for further details).
| 2.1.2 Deleting Applications from the Database HL Applications can be deleted record by record (highlight the Application you wish to delete then click the button labelled Delete the record) or as a block of records (click the button labelled Delete a block of records). The latter will display a dialog box with two block deletion radio button options. Block deletions can be based on a range of dates (the default option) or a range of numbers. If the number range option is selected all applications with an alpha suffix (such as 2022A) will be deleted along with the base HL number (such as 2022). In each case a warning will be given just before deletion begins to give you the chance of cancelling the operation. An 'Undo Delete' button will also appear on the main HL Applications form at the same time as the warning message is shown. Once the delete operation is completed this button becomes active. Clicking this button will restore the database to what it was before the first deletion was performed. Note that multiple single or block deletions can be undertaken in the same session. The session begins when you first open the HL Applications Database window and ends when you exit from it. Once the HL Applications window is closed it will not be possible to restore the original database through the program interface. It can, however, be restored manually using Windows Explorer. Navigate to the "..\Tempfiles" folder and copy all file names containing the word "-Backup" into the "..\Applications" folder. Delete, or rename, existing files in that folder then remove the word "-Backup" from the newly copied files.
2.2 Heavy Load Application Numbers
| HL Number This is a unique integer number that identifies the HL Application being processed. Applications are saved to, and retrieved from, the database using this number. It must, therefore, be unique. If you do save your Application to the database this number will also be saved by HLR and interrogated when the program is next run (it is saved to a text file called LastApplication.dat in the ..\HLR\Database\ subdirectory). The value stored there-in will then be incremented by 1 to create the number for the current run. Note, however, that if you have loaded and re-analysed an existing Application from the database this number will not be incremented. There is no requirement to save the Application to the database if you do not wish to. If you do, however, a valid alpha-numeric identifier must be specified - the Application will not be saved if this field is left blank. Use any text editor (such as Notepad) if you wish to change, or reset, the number in LastApplication.dat (located in the ..\HLR\Database\ subdirectory. Application Number This represents the job or order number that generally appears on an application form received for processing. It is included for documentation purposes only and is not used within HLR for any other reason. It may be ignored if not required.
2.3 HL Applications Database
| Applications are stored as a number of ASCII (text) files in the ..\HLR\Database\Application subdirectory as follows:
HLA1.TXT | Each row represents one application. The fields only contain data from the Job ID tab.
HLA0.TXT | Each row represents a single data value from the Analysis Options tab, the first record always being the application number and the others representing the flags and values.
HLR1.TXT HLR2.TXT | These two files contains route information associated with each application. The structure of each file is identical to that of the route files themselves, with the exception that the first field in each record represents the application number.
HLV2.TXT HLV3.TXT | These two files contains vehicle information associated with each application. The structure of each file is identical to that of the vehicle files themselves, with the exception that the first field in each record represents the application number.
Note that reports and log files associated with the application are not loaded - you will have to re-run the analysis in order to regenerate them. Refer to Clause 2.1.2 above if you want to delete one or more HL Applications from the database.