What's New in FH 6

Below is a list of new features and issue fixes as drawn from our support database.

  • When the FH Enterprise Archive completes, you are prompted that the archive location is C:\Program Files\FIREHOUSE Software\Archives\Arch2002. You should be prompted with the SQL Database name that was created. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.92 Earliest: 0.0.0 Fixed: 6.0.8
  • It does not appear that the LastBackup Date in the FHDATA.INI is being updated if the backup utility is run outside FH. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.67 Earliest: 5.0.0 Fixed: 6.0.16
  • Restored backups are incomplete when the directory structure on the computer where the backup was created and the computer where the files are restored are different. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98
  • If 'Backup To' is disabled when running the backup utility outside of FH, it is most likely because the FH Enterprise database name does not start with FH. FH Enterprise databases are no longer required to start with 'FH'.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.14
  • FH Enterprise is not keeping the device name entered for an Automated Tasks. When the SQL backup command is used by non-FH applications using a device with a name that sorts earlier than the FH Enterprise backup device, the non-FH database device name is adopted by the FH Enterprise backup task.

    A temporary solution in FH 5 is to create a new backup device in FH called 'afhbackup'.

    This problem has been fixed.
    *** Version Information ***
    Reported: 5.5.10
  • Enable detailed audit tracking for the FH Enterprise version. Detailed audit tracking is enabled via the Administrative Options Database section Auditing section.
    *** Version Information ***
    Reported: 5.1.16
  • The SQL Server account that you log in as either needs DB administrative or DBO rights to access the admin/user fields option. If a message appears stating 'You do not have adequate rights to update userfields', rights is the issue. When using the "Use Windows NT Authentication" when setting up the Remote Configuration Utility (or FHODBC) the user security to access the admin.user fields area is not being passed correctly. This problem has been fixed.
    *** Version Information ***
    Reported: 5.2.11 Earliest: 0.0.0 Fixed: 6.0.18
  • Optimized FH Enterprise printed reports. Updates and new report forms are now quickly downloaded from the server to the client when new or updated report forms have been added at the server.
    *** Version Information ***
    Reported: 5.3.24
  • Some upsizing error message boxes include incomplete error information. The number of errors is listed but no additional information is included. This problem has been fixed.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.0
  • A client added multiple users in FH Enterprise using the same 11 character password. Attempting to access FH using any of the user logins resulted in an "Invalid user name or password" message. Changing the password remedied the problem. Certain password string combinations were found to be incompatible with the encryption method used by FH Enterprise. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.80 Earliest: 5.3.24 Fixed: 6.0.21
  • A report will not run as an automated task in Enterprise if the query has FoxPro functions. This problem has been fixed.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.0
  • FH Enterprise does not update audit records when connected using the ODBC data source method. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.31
  • If you are running FH 5.4 tools with Validate File locations and you are missing the CDX and database container files, when you specify in the Advanced area that this is a Data and Lookup folder, a message about Orphaned files is displayed and all DBF files are marked as Orphaned. You must cancel this Duplicate Files window and tools complete. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.65
  • Enhanced database tools automatically expands a new remote database directory when reindex is selected. This saves a step in resolving some FH Enterprise database issues.
    *** Version Information ***
    Reported: 5.4.0 Earliest: 0.0.0 Fixed: 6.0.4
  • Single-click replication of existing Vitals/Assessments, Procedure, and Medication records. Allows you to quickly add additional records with major data elements already included.
    *** Version Information ***
    Reported: 5.0.62 Earliest: 0.0.0 Fixed: 6.0.0
  • Relaxed EMS incident Patient record save requirements. When 'save incomplete incidents' is enabled via Administrative Options, you can save an EMS patient record with limited information. Additional information is required to complete the patient record but the patient record can be saved and completed later.
    *** Version Information ***
    Reported: 5.0.68
  • Enhanced medication lookup codes, can now include default dosage information (measure, units, route, and a text field for a description and/or other instructions). Default information is inserted into patient medication records when the medication code is used.
    *** Version Information ***
    Reported: 5.0.70
  • Enhanced EMS Patient narrative. Added a new auto-generated narrative template for EMS patient records that summarizes EMS incident report information and a comprehensive overview of patient information including signs and symptoms, past medical history, medications, treatments, and assessments, etc. Auto-Generate is enabled via the Administrative Options form Incident section EMS/Search & Rescue section 'Auto-Generate Narratives' option and added to the EMS Patient record from the Patient/Victim Information form Patient Narrative section by pressing Auto Generate (after patient information has been added). Select the 'EMS patient - System supplied default' template and press Generate, then OK to add the information to your EMS patient narrative.
    *** Version Information ***
    Reported: 5.0.0 X Earliest: 0.0.0 Fixed: 6.0.20
  • Right mouse click the assessments and treatments listing in EMS patient records is not sorting the list. This problem has been fixed and enhanced. Lists can be sorted ascending or descending, columns can be moved and resized, and the changes to lists can be saved.
    *** Version Information ***
    Reported: 5.3.15 Earliest: 5.2.41 Fixed: 6.0.29
  • The Ohio EMS export was not exporting EMS incidents when the City field is ALL CAPS. This problem has been fixed.

    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.10
  • Enhanced patient time entry allows '99:99:99' (Unknown/Not Determined) and '88:88:88' (Not Applicable (Time)). Response time analysis will not calculate values for not determined/not applicable time fields.
    *** Version Information ***
    Reported: 5.4.52 Earliest: 5.3.24 Fixed: 6.0.44
  • When the EMS/Search & Rescue Report form 'No Patient' field is checked, the tab order skipped the Scene section (note that the 'Scene' section is now named the 'Patient/Victim' section and previous scene information has been moved to the 'Basic' section). This problem has been fixed.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.0
  • Default date for procedures, medications and vitals is based on the date from the last record in that area (e.g. procedure dates won't default from medication record dates). If there is no last record, the first ptient record non-empty date in the chain of Arrived Pt, Arrived Scene, Unit Notified is used. The Unit Notified date is defaulted by the system as the Alarm Date.
    *** Version Information ***
    Reported: 5.4.87 Earliest: 0.0.0 Fixed: 6.0.4
  • Enhanced Vitals, Procedures, and Medications records. Add user fields and attachments to EMS patient Vitals/Procedures/Medications records.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.18
  • The Injury Matrix can be added even when Injury/Illness, Injury Intent, or Mechanism do not indicate Injury. Useful for EMS reports where injuries occur as a result of another condition (for example, a seizure patient who has suffered an injury because of that seizure).
    *** Version Information ***
    Reported: 5.0.0
  • Added HIPAA notice tracking. Accessed from the EMS Patient/Victim Information form Disposition & Transport section Privacy Policy Status button. You can indicate the date and whether the HIPAA notice was given during call, mailed (with a date field next to the button description), or select Other (and type a 30 character description) if necessary.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.33
  • Enhanced patient recall. When entering an EMS patient that is a former patient, selecting the patient from the list brings in phone numbers in addition to the basic address information.
    *** Version Information ***
    Reported: 5.4.98
  • for the Standard EMS Transaction, the max length of staff ID is 15, the documentation for the standard EMS Transaction is 15, but we only export 9 characters. This problem has been fixed to export 15 characters.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.10
  • Added a Reason for Transport field to the Patient/Victim Information form Disposition & Transport section. The 50 character text field lists entries made in other records, simplifying data entry.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.19
  • Enhanced incident narrative control. Lock narratives and allow non-administrative users to only append notes to fire, EMS, EMS patient, and investigation narratives. Enabled via the Administrative Options form Incident section General section 'Allow only appending to narrative" option. When enabled, an additional option is available in the user's security profile to allow the non-administrative user to unlock narratives.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.16
  • Added an option to the EMS Export Wizard to exclude patient billing information, providing additional control over patient information.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.15
  • Added 'Same as Alarm' checkbox to Vitals, Procedures, and Medication Dates. Enables these dates to remain synchronized with the alarm date if the Alarm Date is changed in a renumber. For advanced users: Also allows a default value of .T. to be set on these fields via System Rules and Default Values to default the alarm date in these fields.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.37
  • Added the ability to multi-select personnel in procedures and precautions.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.44
  • Mechanism of Injury for MO EMS Codes includes code "30 - Other Unknown Injury". Should be "30 - Other Known Injury". This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98
  • Enhanced system rules. Adding requirements for fields that can include '0' values (for example, a '0' for EMS Patient vitals pulse rate indicates that a pulse rate is absent) displays an additional prompt to allow the '0' value.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.46
  • The following code additions and changes have been made for FH 6 Indiana EMS reporting:
    EMS FACIL Transport Destinations/Facilities
    5430 from St. Franics Hospital Center
    to St. Francis Hospital and Health Center
    5480 from St. Mary's Medical Center of Evensille
    to St. Mary's Medical Center of Evansville
    5615 from Vencor Hospital
    to Vencor - LaGrange Hospital
    Added:
    O127 St. Mary's Hospital - Evansville - East
    O435 Bickford cottage Extended Care - Wabash
    7115 Indiana Heart Hospital - Indianapolis
    7120 Americare
    7125 Willowbend

    EMS LEVEL Level of Provider
    from I EMT-I (ADVANCED)
    to I EMT-I (INTERMEDIATE)

    Added:
    E EMT-BA (BASIC-ADVANCED)
    *** Version Information ***
    Reported: 5.4.99
  • Changing your EMS codeset after EMS incidents have been entered is not recommended. We have added additional prompts that must be completed before a new EMS code set can be installed.
    *** Version Information ***
    Reported: 5.5.6 Earliest: 0.0.0 Fixed: 6.0.33
  • The Ohio EMS lookup code for location type has a code 04. The description is 'Industrial place and premisis". Premisis should be spelled premises. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98
  • After entering times for an EMS/Search & Rescue Report and adding a Responding unit record, pressing certain keystroke combinations (e.g., ALT + R) disables dates and times in the Response section for patient record added using the unit. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.29
  • User-defined fields can now be added to EMS patient procedures and medication records.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.33
  • When an EMS transaction file is imported and there are certain conditions that exist in the transaction file, an 1884 error is generated and the import process is interrupted. This problem has been fixed so that the import will complete and any errors and exceptions are written to the log file.
    *** Version Information ***
    Reported: 5.5.10 Earliest: 0.0.0 Fixed: 6.0.54
  • When Procedures, Medications, or Vitals are required and not added to a patient record, the Assessments & Treatments section is color-coded to indicate that required information has not been added, but the validation results does not list the missing Procedures, Medications, or Vitals. This directly effects some state EMS systems (e.g., Ohio). This problem has been fixed.
    *** Version Information ***
    Reported: 5.5.10 Earliest: 0.0.0 Fixed: 6.0.51
  • Enhanced patient exposures and precautions. When adding staff to an exposure or precautions detail record, you can select 'All Responding Personnel' or (if the optional staff scheduling module is enabled) 'All Scheduled Personnel'.
    *** Version Information ***
    Reported: 5.5.2 Earliest: 0.0.0 Fixed: 6.0.38
  • Added a Description area for adding notes and comments about external import definitions. Departments can save information about the Import External Data definition without affecting the import. For example, you can use the notes to document what the definition does.
    *** Version Information ***
    Reported: 3.0.0 Earliest: 0.0.0 Fixed: 6.0.16
  • Enhanced activity timeout. Automatically log a user off if there is no activity for a preset time. Accessed via the Administrative Options form General section.
    *** Version Information ***
    Reported: 3.0.0 Earliest: 0.0.0 Fixed: 6.0.0
  • Auto-Narratives for NFIRS incidents, EMS incidents, EMS Patient records, and Investigation records. Narratives are created using a template that draws data elements from various sources, including free text, field values from related records, and reports that display related information. Advanced users can modify existing templates or create new templates.
    *** Version Information ***
    Reported: 5.0.58 Earliest: 0.0.0 Fixed: 6.0.19
  • Required check boxes and selection fields are color-coded like tabs and fields.
    *** Version Information ***
    Reported: 5.0.68
  • Added background auto save. Enabled and specified via the Workstation Options form General section Data Entry Forms subsection.
    *** Version Information ***
    Reported: 5.0.70
  • Require additional confirmation before allowing master records to be deleted. Enabled from Administrative Options (Tools menu>Workstation Tools option>General section>Data Entry Forms subsection>Confirm master record deletion by typing "Yes" checkbox), when the Delete button is pressed from any master record data entry form, the Confirm Delete dialog is displayed listing the specific record to be deleted. 'Yes' must be typed before the listed record can be deleted.

    NOTE: You can also opt to completely hide the "Delete" button from data entry form (this applies only to the delete button at the bottom of the form, not to delete in grids).
    *** Version Information ***
    Reported: 5.1.7 Earliest: 0.0.0 Fixed: 6.0.29
  • Select the current date in the Department Journal form via the Options button Today option.
    *** Version Information ***
    Reported: 5.1.24 Earliest: 0.0.0 Fixed: 6.0.26
  • Enhanced Daily Reminder notes. Specify a date for deleting a note added to the Daily Reminders area and the note is automatically deleted after the specified data.
    *** Version Information ***
    Reported: 5.1.24 Earliest: 0.0.0 Fixed: 6.0.20
  • First arriving unit is listed for incidents displayed in the Department Journal.
    *** Version Information ***
    Reported: 5.1.24 Earliest: 0.0.0 Fixed: 6.0.15
  • Expanded detail record entry. Added user fields and attached files to Unit Response Detail records, Participant Detail records, and Attendee Detail records.
    *** Version Information ***
    Reported: 5.2.18 Earliest: 0.0.0 Fixed: 6.0.18
  • Added 'No Patient' checkbox to the Dispatch/Remote Station Incident Report form to allow dispatchers with limited access to note this information.
    *** Version Information ***
    Reported: 5.1.24 Earliest: 0.0.0 Fixed: 6.0.2
  • Enhanced incident report entry. When responding personnel are entered for an incident and you lookup staff (for example, adding staff to an authorization record) a list of staff based on responding personnel is available.
    *** Version Information ***
    Reported: 5.2.21
  • Users with Add and View rights can not save records that they add and renumber. This problem has been fixed so users with Add and View writes can add, renumber, and save the added record.
    *** Version Information ***
    Reported: 5.3.23
  • Expanded automatic log purging. Specify that selected database logs be purged at user-defined intervals. Available logs are the audit log, the user login history log, the automated task log, the export to station log, the import from station log, the external data export log, the PDA import/export log (for FH Onsite Inspections), and the custom data export log.
    *** Version Information ***
    Reported: 5.4.38
  • Queries that are sorted by expressions that include FH functions (e.g., StaffName()) may not run properly or return the expected results. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.41
  • The spell check dictionary files cannot be located for certain clean FH installations. The dictionary files are installed and can be found via the Administrative Options form. This problem has been fixed so that the spell check dictionary is located for all FH installations without requiring the user to locate the dictionary files.
    *** Version Information ***
    Reported: 5.4.46
  • Enhanced Staff ID selection. In fields where a Staff ID is selected and the Staff ID value is likely to be the currently logged in user (for example, in a member making report form), the Staff ID associated with the current login is displayed in the lookup when completing the field. In fire and EMS incident reports, staff members added as responding personnel are also listed. You can still select other Staff IDs if necessary.
    *** Version Information ***
    Reported: 5.4.54 Earliest: 0.0.0 Fixed: 6.0.26
  • The Department Journal form displays events filtered by shift incorrectly. When an event starts and finishes at the same times the shift filter does, the event is displayed on two days (should only display on one day). This problem has been fixed so that an event that starts and ends on the shift filter start and end time is only displayed in that day on the journal>.
    *** Version Information ***
    Reported: 5.4.62
  • The Administrative Options form lists stations sorted by FDID then Station. This simplifies station code management for regional reporting agencies that receive incident reports from multiple departments.
    *** Version Information ***
    Reported: 5.4.65
  • When the Login form is displayed as a result of inactivity, and you press Exit, in certain circumstances you get Error 1924: OFORM is not an object at line 46 of procedure/method APP.LOOKUP.OPTIONS. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.63 Earliest: 0.0.0 Fixed: 6.0.4
  • The ParseAddress function Advanced Function Detail form lists the values for the expN parameter incorrectly. 3 should be Street Name and 4 should be Street Type. The descriptions are now accurate.
    *** Version Information ***
    Reported: 5.3.24
  • Enhanced field navigation, when number fields are selected the entire field is highlighted for entry.
    *** Version Information ***
    Reported: 5.4.67 Earliest: 0.0.0 Fixed: 6.0.16
  • User-Defined Field form size is specified as part of the form design. User-defined field forms are accessed from the Administration menu>User-Defined Fields option.
    *** Version Information ***
    Reported: 5.4.69 Earliest: 0.0.0 Fixed: 6.0.4
  • Enhanced Daily Reminders listing saves the order reminders are last displayed in. Click a column title to sort by that column in ascending order (A to Z), or right-click a column title to sort by that column is descending order (Z to A).
    *** Version Information ***
    Reported: 5.4.71 Earliest: 5.3.24 Fixed: 6.0.15
  • Enhanced Department Journal filtering. Workstation option to automatically filter displayed journal events based on workstation information. When enabled, the journal and daily reminders will only display events for the station associated with the workstation. Enabled via the Workstation Options form.
    *** Version Information ***
    Reported: 5.3.24
  • Report and Graph favorites: If there are too many favorites reports some reports are not accessible. This problem has been fixed so that favorites are listed by module, and favorites can be displayed in the Reports/Graphs form by checking 'Favorites Only'.
    *** Version Information ***
    Reported: 5.3.24
  • Additional auto-generated key values for work order numbers in inventory maintenance/test detail records, and for department course number for training class records. Enabled from the Administrative Options form Database section Key Values section. These fields include a 'magic wand' button that, when pressed, generates the next sequential available number.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.26
  • FH fails when importing external data and using the PARSEADDRESS() function when the address includes a user-defined street type. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.74 Earliest: 0.0.0 Fixed: 6.0.15
  • Enhanced attachment security. When 'Security for Attachments & Signatures" is enabled via the Administrative Options form Database section Attachments & Security subsection, non-administrative users must be granted rights to access attachments in their individual user security set up.
    *** Version Information ***
    Reported: 5.4.74 Earliest: 0.0.0 Fixed: 6.0.42
  • Added a Requery button to the Department Journal form. Press to display records added from other workstations while the Department Journal form is displayed. Accessed from the File menu>Department Journal option Requery button.
    *** Version Information ***
    Reported: 5.4.7 Earliest: 0.0.0 Fixed: 6.0.0
  • When an exit or logout button has been added to a custom toolbar, and you press the custom exit/logout button with a master form (for example, the EMS/Search & Rescue Report form) and a child form of the master form (for example, Patient/Victim Information form) the child form is closed without saving any changes. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.77 Earliest: 0.0.0 Fixed: 6.0.25
  • You can setup the same login name multiple times, although this is not recommended. Added a prompt that is displayed when adding a user name that already exists. Duplicate user names + password combinations are not allowed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.33
  • Added District, Shift, and Zone fields to the Export Data to Station form, adding more filter options for exporting stations to use in selecting records to export. Accessed from the File menu>Station Management option>Export to Station option.
    *** Version Information ***
    Reported: 5.4.80
  • Child records like unit response details created via external data import (for example, imported from a CAD system) are not indicated as incomplete via color-coding when the incident record is reviewed in FH. This problem has been fixed so that when rules exist requiring certain values in a child record and the values are not included, FH will show these detail records as incomplete using color coding (for example, the responding units area of the incident report will be color-coded to indicate that a required value is missing when a requirement is not met in an imported record).
    *** Version Information ***
    Reported: 5.4.81
  • Added lookup buttons to the Supplemental Address form Latitude and Longitude fields.
    *** Version Information ***
    Reported: 5.4.81
  • Enhanced password control. Set password requirements including minimum length, frequency at which the password must be changed, and whether password must contain numbers and/or special characters. This is controlled via the Administrative Options form General section. Also added the ability to force a password change for a specific user from the Users and Setup form.
    *** Version Information ***
    Reported: 5.4.8 Earliest: 0.0.0 Fixed: 6.0.29
  • Clicking on or tabbing through any notes field, (even without changes) and pressing Esc marks the record as modified. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.82
  • Enhanced Security Timeout. When the Inactivity timeout is enabled (Administration menu>Administrative Options option>General section>Security area) you are automatically logged off when there are no unsaved changes. When a form with unsaved changes is opened at timeout, the workstation is locked and you are prompted to enter a password into the Security Timeout form. FH considers this workstation to be 'in use' and counts it in calculating the total number of licenses in use. To conserve licenses but lose unsaved changes in a timeout, enable Force logout even if changes would be lost (Administration menu>Administrative Options option>General section>Security area)
    *** Version Information ***
    Reported: 5.0.0
  • Enhanced user-defined field control with the ability to disable a user-defined field based on conditions (for example, the value of another field) and the ability to exclude user-defined form sections. Set disable conditions via field properties. Conditional section exclusion is controlled via the Form & Table Properties form Pages section.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.49
  • Disabled user accounts are hidden in the Users and Security section. Check Show Disabled User Accounts to display disabled user accounts.
    *** Version Information ***
    Reported: 5.4.80
  • When deleting a workstation listed multiple times, after deleting the second duplicate workstation you get Error 1234: Subscript is outside defined range. This problem has been fixed.
    *** Version Information ***
    Reported: 5.2.41 Earliest: 5.2.41 Fixed: 6.0.0
  • Global date validation checks year and prompts for confirmation when outside a certain range to prevent bad dates from being entered (for example, 01/01/0001 would result in a prompt).
    There are basic relational edits in FH regarding dates. For example, date of alarm on incident report cannot be later than the current system date. These are rule-driven. The global date validation prompt the user for verification if the date entered is outside of a date window which goes 150 years before and after the current system date. There are also date of birth fields that perform a global date validation and additionally will not allow a date of birth greater than the current system date (that is, born next week). A list of fields is available in the FH Help File 'Date Validation' topic.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.41
  • When a lookup code in a lookup table is empty and 'Default Sort by Description' and 'Show Hidden Codes' are checked in the 'Lookup' form, ALL lookup codes for the table are displayed. Codes can not be added to records. The workaround in FH 5 was to install preset codes for the lookup table or add a code for the category. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.6
  • While importing CAD data via an automated task, you get an error Variable 'MESSAGE' is not found. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.74
  • Accessing the report layout area of a printed report form while date entry forms are open can result in an Error 165: Menu has not been defined with DEFINE POPUP in certain circumstances. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 5.0.81 Fixed: 6.0.6
  • User-defined fields can be added but not displayed in user-defined field forms. Fields that were not displayed were not available to be readded to the form. This problem has been fixed. The 'displayed' status of the user-defined field is available from the Form & Table Properties form Table section, and you can add an undisplayed field to the user-defined field form by adding a new field and selecting the undisplayed field from the Field Name field.
    *** Version Information ***
    Reported: 5.4.98
  • When in User-Defined fields area, go to Form and Table Properties for this, under the Table tab, when you delete all user fields, the last user field is still listed (it is properly deleted). This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98
  • Enhanced lookup code entry allows users to type in the initial characters or a keyword of the lookup code description. Tab through the field and a list of matching codes is displayed (or the lookup is filled in if there is only one code matching entered text). The lookup code description field is skipped when Tab is pressed if a lookup code has been selected. See the FH Help File 'Workstation Options' form 'General' section 'Startup & Navigation' section topic for more information.
    *** Version Information ***
    Reported: 5.4.98
  • Files transferred via the FH Internet File Transfer form can have additional characters added to the file name and path, creating problems that can prevent the uploaded file from being downloaded and used. This problem has been fixed.
    *** Version Information ***
    Reported: 5.2.4 1 Earliest: 0.0.0 Fixed: 6.0.10
  • If you are importing from a folder on a different machine and you do not have that folder set up as a mapped drive, and you have the delete source record after import checked it does not delete the source file after import. If you have the folder you are importing from set as a mapped drive it will delete the source file.
    This problem has been fixed so that source records on unmapped drives are deleted when so specified.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.4
  • When you modify an existing records notes or narrative field and add to it then press ESC changes are not saved. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.0 Earliest: 0.0.0 Fixed: 6.0.4
  • When you open a lookup code category to edit, then FH times out (time out is enabled) then log back in, you will get an error 1924: OFORM is not an object at line 46 of procedure/method APP.LOOKUP.OPTIONS. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.0 Earliest: 0.0.0 Fixed: 6.0.4
  • When a browse list is displayed, you can type text and FH will highlight the first listed record with matching text. The search launches after a short interval, but the interval was defaulting to be too long. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98
  • Added the ability to add default values based on values entered in other fields on the same form. To set up, access the field in system rules and default values, add an 'Update the Value of Another Field...' rule and select the field to replace, when to replace it, and the value to insert into the specified field.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.36
  • Enhanced data entry form exit, when unsaved changes exist and you press 'Cancel' you have three options:
    Save Changes, Discard Changes, or Cancel (Cancel returns back to the form).
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.25
  • Display a custom graphic to the FH workspace background. Accessed from the Tools menu Workstation Options option from the General section Desktop subsection.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.10
  • Added a Units & Personnel section to Fire and EMS incident report forms. The Units & Personnel section replaces the Responding Units and Personnel & Activities buttons that were included in the Additional Records section of FH version 5 incident report forms.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.14
  • A copy to of a programmed report will only get the first layout, it will not get all of them. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98
  • The FH Installation places KeyLib32.dll in the FH root folder, not windows\system32, to prevent version conflicts with other software that may install the DLL and also prevents other potential errors
    *** Version Information ***
    Reported: 5.4.98
  • Start up Dispatch, NFIRS or EMS and start tabbing through to create a record. When you tab to time it will put the system time in and then tab to go to the Incident number it will replace the hours with 03 from the incident number and then not allow you to tab anywhere. The only workaround is to access the Tools > Workstation Option and check 'Highlight field on entry'.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.20
  • Optimized database views for faster data entry form loading.
    *** Version Information ***
    Reported: 5.5.0 Earliest: 0.0.0 Fixed: 6.0.14
  • When users are imported via Export To/Import From Station and specific security groups have been associated with individual users, the group associations are not displayed. Each member is granted the permissions of that group. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.20
  • There is a conflict with the FH spell check and Earthlink software. When you run the FH spell check utility and Earthlink is installed on the workstation, you gert: Error 1426: OLE error code 0x80040154: Class not registered. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.16
  • New module for FH 6, FH Accounts Receivable. This module allows customers to invoice and track payments for accounts they set up (can be linked to occupancies or other areas) and then bill the accounts for things such as false alarms, inspections, activities, training, etc. The FH Accounts Receivable module is an extra cost option.
    *** Version Information ***
    Reported: 5.4.99 Earliest: 0.0.0 Fixed: 6.0.22
  • Record lock status displayed in the incident report Other section is not being updated properly when a non-administrative access user browses multiple records. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98
  • Add a user-defined requirement for a record area (training class user fields for example) and the form section where the user0defined field is completed (Training form Other section) is not indicating that the user-defined fields are not complete. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98
  • FH shortcut startup options do not work for the Journal
    (Target="C:\Program Files\FH54\FH.EXE" L=JOURNAL).
    This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98
  • "Enable Basic Database Audit tracking" must be enabled in Administrative Options to allow non-administrative users to view EMS patient records they created, to export records to station, and to auto lock records for 'User Level' or 'After Initial Entry ### Hrs'. Added an additional prompt to the Administrative Options form Database section Auditing section that is displayed when disabling the "Enable basic audit tracking" feature to communicate these relationships.
    *** Version Information ***
    Reported: 5.4.98
  • For advanced users: Added the ability to require a record in AUD_LOCK for fire and EMS incident records, requiring that fire and/or EMS reports be manually locked before being saved.
    *** Version Information ***
    Reported: 5.4.99 Earliest: 0.0.0 Fixed: 6.0.38
  • FH Enterprise audit logs are not automatically purged in certain configurations where records are created at a workstation via CAD import. This problem has been fixed. The log is purged any time a last purge date is unavailable or any time the last purge date is less than the current system date.
    *** Version Information ***
    Reported: 5.4.98
  • In certain instances, VSLINK.DLL becomes corrupted. When you access the Workstation Options form Other section and select to auto load on Windows startup and VSLINK.DLL is corrupted you get an 'error 1754: Cannot find entry point CreateLink in the DLL. at line 41 of procedure/method'. This problem has been fixed.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.19
  • If a text label is created on a user-defined field that includes a carriage return, you can save the user field change, but when you open the user field definition, you get: Invalid Label format "<unique code>". There is no access to edit it. This problem has been fixed.
    *** Version Information ***
    Reported: 5.5.3
  • Enhanced Department Journal filtering. Journal filter options limit records requested from database for improved display times (results in less data from database when filters are specified). When a filter is modified, the FH database is requeried.
    *** Version Information ***
    Reported: 5.4.98
  • When multiple user-defined radio buttons are added and you enter values for data entry, in certain circumstances, you get an error 11: Function argument value, type, or count is invalid. This problem has been fixed.
    *** Version Information ***
    Reported: 5.0.25 Earliest: 0.0.0 Fixed: 6.0.26
  • Enhanced find in lookup code categories. Improved search quickly finds and displays codes with matching search text or numbers.
    *** Version Information ***
    Reported: 5.5.10 Earliest: 5.4.98 Fixed: 6.0.42
  • Enhanced error reporting, with additional options to email an error report to support (if an Internet connection is available). Also added additional technical information, including line numbers for the entire call stack.
    *** Version Information ***
    Reported: 5.4.98
  • Export to station generates an 'Error 170 Incorrect Syntax Found' when certain characters are used in ID fields (for example, a single quotation mark) and interupts the export process. Export to station will now export to station even if a single quotation mark is included in the ID field, and if characters that cannot be included are encountered, the export process completes and an exception record is added to the export log indicating that a specific record included invalid characters in an ID field.
    *** Version Information ***
    Reported: 5.5.10 Earliest: 0.0.0 Fixed: 6.0.33
  • Users with view only security can delete child records from other modules in certain configurations. This problem has been fixed so that users can only delete records for areas where they are assigned 'delete' rights.
    *** Version Information ***
    Reported: 5.5.10 Earliest: 0.0.0 Fixed: 6.0.38
  • Enhanced save option allows lockable record to be saved and locked in a single step. Right-click on the Save button for the lockable record and select 'Save and Lock', or press Ctrl+K.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.43
  • Enhanced nested category lists. In lists that have nested categories, you can press and hold the keyboard CTRL key while clicking a "+" drill-down button for the category to expand or collapse all the subcategories related to the category. For an example of a nested category list, see the Scheduling Control Panel. Additional examples include the Lookup Tables form, the Reports form, the Queries form, the Maps form, and the Graphs form.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.4 2
  • The Install System Activation Diskette option under the Administration menu allows for locations other than a floppy drive (usually A:) when an activation diskette is not found.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.58
  • When you run a graph and there is no data to return, it opens a blank Graph window. This problem has been fixed so that you are prompted that 'there were no records found'.
    *** Version Information ***
    Reported: 5.4.80
  • Enhanced graphing options, with the ability to save graph display options made while running a graph.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.16
  • Enhanced hydrant management. Automatically prompt to add notes and briefs when hydrant status is changed. When enabled from the Administrative Options form Hydrant section, you are prompted to add a 'notes & brief' record that tracks 'in' and 'out' of service status changes for the hydrant record. Position cursor over 'Out of Service' checkbox to display the most recent status change record. Also added LastServiceStatusInfo function for custom reports. LastServiceStatusInfo takes a HYDR_ID value and a status code (e.g. "IN" or "OUT") and returns a description of the last recorded entry for that status code. This function is documented on the Advanced tab in the Expression Builder dialog.

    Modified the following reports to include status change information:

    Hydrant Field Cards (4 X 6)
    Hydrants Out of Service
    Hydrants Out of Service with Occupancies
    Hydrants by Hydrant Number
    Hydrants by Location
    Runbook of Premises
    *** Version Information ***
    Reported: 5.0.22 Earliest: 0.0.0 Fixed: 6.0.50
  • Added a 'Defects Found' column to the Hydrants form Activities section.
    *** Version Information ***
    Reported: 5.1.24
  • Added Repair Cost field to the Hydrant Activity form Activity/Repair section for tracking costs associated with hydrant repairs and activities. Also included the Repair Cost field on the Hydrant Activities, Repairs, and Flow Tests by Hydrant report.
    *** Version Information ***
    Reported: 5.1.24 Earliest: 0.0.0 Fixed: 6.0.20 E
  • Multiple activites entered for Batch Flow Tests/Activities are not added to all hydrant records selected during batch entry. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.26
  • The NFIRS Incident Report form indicates that there are exposures (if any) in the base incident. The number of exposures are indicated in parentheses after the Exposure field name (if greater than zero).
    *** Version Information ***
    Reported: 3.0.0 Earliest: 0.0.0 Fixed: 6.0.26
  • Add Vehicle Accident/Extrication reports directly from the NFIRS Incident Report form (EMS Search & Rescue Report not required).
    *** Version Information ***
    Reported: 5.0.81 Earliest: 0.0.0 Fixed: 6.0.28
  • Added group edit to the Unit Personnel Response Detail form Personnel section.
    *** Version Information ***
    Reported: 5.1.24 Earliest: 0.0.0 Fixed: 6.0.27
  • Added the Involvement Type field in the Investigation form Lead/Involvement section. This lookup field provides the ability to differentiate between leads, involvements, witnesses, material witnesses, leads, suspects, prime suspects, etc. This provides a secure place to add involvement information.
    *** Version Information ***
    Reported: 5.2.36
  • Enhanced incident resource detail reporting requirements. Require unit details, responding personnel, or personnel detail records for responding units. Requirements are specified from the Administrative Options form Incident section All Incidents subsection Resources, Units & Personnel subsection.
    *** Version Information ***
    Reported: 5.3.23 Earliest: 0.0.0 Fixed: 6.0.38
  • Responding unit entry has been enhanced to simplify entering specific responding unit details and groups of responding units. For the steps to enter unit response detail records, see the User Guide NFIRS Incident or EMS Incident chapters.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.27
  • User-defined fields and attached files can be added for HazMat Reports (accessed from the NFIRS Incident Report form>Additional Reports section>HazMat button).
    *** Version Information ***
    Reported: 5.4.72 Earliest: 0.0.0 Fixed: 6.0.4
  • The Unit Actions Taken button is not color-coded to indicate that it is required when it is required via system rules and default values. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.88 Earliest: 0.0.0 Fixed: 6.0.0
  • When two users access a record and modify narratives, the latter user memo changes are saved without any update conflict. There should be an update conflict message. It is not happening for memo fields. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.0 Earliest: 0.0.0 Fixed: 6.0.18
  • Enhanced NFIRS incident security. Added the ability to limit access to involvement records to administrators and non-administrative users who entered the involvement.
    *** Version Information ***
    Reported: 5.4.93
  • FH allows multiple staff activities for a single NFIRS responding personnel. FH exports the multiple staff activities for the personnel, which causes an error when the incident is imported at the state. This problem has been fixed so only one personnel response record is included for a given personnel for a unit
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.21
  • If you delete an exposure, Responding Units and Personnel are deleted from the base incident report. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.15
  • The 'None' checkboxes on the Wildland Fire Report form Fire section and on the Investigation form Basic section were not automatically adding a 'none' entry to their respective data grid when checked. These problems have been fixed.
    *** Version Information ***
    Reported: 5.4.82
  • If you enter a NFIRS report and don't fill out the time on the Basic tab, then add a responding unit and add the times, times are not populated back to the Basic tab of the main report. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.9
  • Incident records with near an intersection addresses are exported as a 'near an exact address' with the cross street in the directions field. When FH imports this incident, it makes it a 'near-rural address' to save all of the information. If this incident record is exported again, it is exported as a near exact address without an address. This problem has been fixed so that the incident is exported as exact an address and the import pulls them in as close as possible to the original.
    *** Version Information ***
    Reported: 5.4.98
  • Added three fields to responding unit details:
    * Enroute to Destination
    * Arrived Destination
    * Leave Destination
    CAD imports can now bring in EMS times through a unit record and not have to create a patient record.
    NFIC HAS removed the validation that requires last cleared time on basic to be the same as last unit. Added an Administrative Option to allow it to continue to update last cleared on the Basic incident report with the last unit cleared, or turn it off, so that last unit clear can be later than the basic clear time. The logic is:
    If the option to default the basic cleared time is turned on, get the latest cleared scene time from all the units for that incident. The cleared scene time is assumed to be the enroute to destination time IF that time is specified. If that time is not specified then the old cleared time is still used.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.56
  • Added the ability to add and edit units and personnel for a specific incident without opening the incident record. Accessed from the File menu Unit & Personnel Response Entry option. A custom toolbar button can be added if needed. When selected, the Units and Personnel Response form is displayed where you can type or lookup the FDID, Alarm Date and Incident number. The incident must exist to add or edit units & personnel. Units added for the incomplete incident (from CAD import or otherwise entered) are listed. In addition you can add new units. A field is added to the list of responding units that shows whether the record is locked. Additional security access is available to allow access to Unit & Personnel Response Entry without providing access to Fire and/or EMS incident records. Responding unit records are not automatically locked, but can be manually locked

    Unit detail records can be manually locked. Unit detail records are not automatically locked. When a unit record is manually locked, non-administrative users who did not add the record will not be able to edit the locked unit, even from the main incident record. Units, Personnel, & Equipment locking behavior is specified from the Administrative Options form Incident section All Incidents subsection Authorization & Locking subsection.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.56
  • If a fire is NOT an exposure fire and you put as the Factor Contributing to Ignition (on the Fire tab of the Fire Report Form) code 71 Exposure Fire this does not cause an invalid condition. The incident will be rejected at the state level because it is not an exposure fire and is invalid. This problem has been fixed to prompt the user that the incident is invalid when the incident is saved.
    *** Version Information ***
    Reported: 5.2.41 Earliest: 0.0.0 Fixed: 6.0.19
  • FH allows multiple Human Factors even when one of the factors equals 'None'. This problem has been fixed so that when 'none' is selected as a factor, no other codes are added.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.51
  • Changed label on the tabs from Incident Notes and Unit Notes to Incident Narrative and Unit Narrative.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.12
  • Incident response related personnel are added from the Units & Personnel section of the incident form. Staff activities that are related to the incident (but not incident response activities) are added from the Additional Reports section. For example, a follow up investigation activity would be added to the Additional Reports section. Staff activities not related to incident response are not displayed in the Units & Personnel section.
    *** Version Information ***
    Reported: 5.4.12 Earliest: 0.0.0 Fixed: 6.0.20
  • Evidence Collection Method codes are protected and can not be modified (plus-one codes are allowed). There are no NFIRS requirements to protect these codes. New FH 6 systems will allow code changes and existing FH users can unprotect the Evidence collection Method codes by installing the UNPROT_IVG_METHOD_OF_COLL.FH6 file that is included in the FH6 /TOOLS folder on the installation CD.
    *** Version Information ***
    Reported: 5.4.99 Earliest: 0.0.0 Fixed: 6.0.33
  • The Civilian Fire Casualty Report form Address & Phone entry allows multiple blank telephone numbers to be added. This problem has been fixed so that empty phone number entries are not allowed.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.27
  • When a dollar loss/value is entered via the NFIRS Incident Report form Property & Involvement section then changed the dollar lost/value in the Loss & Value Report, the Update Loss and Value Amounts? prompt reverses the values (lists the original value as the new value) but properly updates values. This problem has been fixed so that updated value/loss amounts are listed properly.
    *** Version Information ***
    Reported: 5.5.6 Earliest: 0.0.0 Fixed: 6.0.26
  • The Involvement form Phone Numbers data grid allowed multiple blank phone numbers to be added and the involvement record could be saved without completing the phone number details. This problem has been fixed.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.22
  • If you add a unit or change a unit arrival and cleared date and time it does not update first arrival and last cleared on NFIRS basic when the arrival of the unit is earlier than the first arrival and/or the unit cleared is later than the last cleared. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.26
  • In certain circumstances, an incomplete incident is marked complete when accessed from FH and saved, even though required elements are incomplete. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.38
  • When entering the name into a new Involvement record that matches previously entered involvements, you can transfer the previously entered involvement information to the new record. The age was not properly calculated. This problem has been fixed.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.29
  • NFIRS import is failing due to lower and mixed case field values. In specific circumstances, lower and mixed case values are included in the NFIRS export file, causing error on import at state. For example, system default values can be added that insert lower case values into fields included in the export. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 E Earliest: 0.0.0 Fixed: 6.0.33
  • The Detector Alerted Occupants field in the NFIRS Incident Report form Response section is required when Mutual Aid Given equals 3, 4, or 5 and the Incident Type is 100 or between 113 and 118 although the NFIRS specification specifies that it should not be. This problem has been fixed so that the Detector Alerted Occupants field is not required if Mutual Aid Given or Received equals 3, 4, or 5.
    *** Version Information ***
    Reported: 5.5.10 Earliest: 0.0.0 Fixed: 6.0.37
  • Add a rule to require Mutual Aid detail on a condition, and the detail button does not change to indicate that the mutual aid detail record is required. This problem has been fixed.
    *** Version Information ***
    Reported: 5.5.10
  • Enhanced staff scheduling integration with responding units and personnel. Select units to add to incident reports from scheduling. To add units indicated as available in scheduling, from the incident report 'Units & Personnel' section, press 'Add' and units added for the active schedule can be selected directly. Press 'Add Group' and if the incident 'Station' value matches the station value for staff entered for the current schedule, select 'All units for station'<name> to add all units entered for the active schedule from station <name>. From the Unit Response Detail form Personnel section, all staff scheduled for the displayed unit can be added by pressing 'Add Group' then pressing 'Add from Scheduling'. Add all scheduled personnel to an incident without accessing the unit detail record by pressing 'Add Group' in the Personnel area. Typically staff will be added from the responding unit detail, but when unit detail records are created from a third-party CAD system, this feature will be useful.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.38
  • Track additional time fields for EMS Search & Rescue time tracking for NFIRS/Dispatch/EMS responding units. Will automatically complete EMS patient times when completed in
    responding unit records.
    *** Version Information ***
    Reported: 5.5.10 Earliest: 0.0.0 Fixed: 6.0.57
  • Reinstalling FH using the previous installation settings resets the registry to open Demodata not Data. (regardless of original option). This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.95 Earliest: 0.0.0 Fixed: 6.0.19
  • The FH licensing file is inserted in the wrong location in new activated systems. The incorrect license file location is not an issue until 'validate file location' is run by database tools or on start up, then you are prompted to remove the license file and the FH licensing is disabled. This problem has been fixed.

    You can now exit the FH 5 CD installation menu. Now complete the following steps:
    A) Access the FH root directory (the FH root directory
    is "C:/Program Files/FIREHOUSE Software/" by default,
    yours may be different) using Windows Explorer.
    B) Highlight the FH.LIC file, then from the Windows Explorer
    "Edit" menu, select the "Cut" option.
    C) Open the "SYSTEM/" folder, then from the Windows Explorer
    "Edit" menu, select the "Paste" option.
    Congratulations, you have activated your FH system. You can start FH.


    Install; FH5Activ puts lic files in root
    fh.lic
    fh.lbk
    fhserial.lic

    *** Version Information ***
    Reported: 5.5.10
  • There is no path defaulted for the FH program during a new installation of FH Enterprise. This problem has been fixed.
    *** Version Information ***
    Reported: 5.0.45 Earliest: 0.0.0 Fixed: 6.0.49
  • Enhanced Maintenance/Test Detail record entry. Add multiple job codes from the Maintenance/Test Detail form to create separate records for each job code. All records added from Maintenance/Test Detail form are linked, and certain record values can be applied to all linked maintenance/detail records.
    *** Version Information ***
    Reported: 3.5.0 Earliest: 0.0.0 Fixed: 6.0.28
  • Enhanced usage lookup code can be defined to default 'add' or 'use' option when used in Usage records.
    *** Version Information ***
    Reported: 5.0.26
  • Enhanced usage details. When a generic equipment record is used on an inventory record, details about the link are included in the Usage/Purchasing Detail record. For example, if you add a usage record from a master inventory record (for example, apparatus) indicating that a generic inventory item was used (for example, an air filter), then later review usage details from the generic equipment, details about where that item was used are available in the Usage/Purchasing Detail form Link Details section.
    *** Version Information ***
    Reported: 5.1.16
  • Added 'License Plate' field to the Inventory form Specs... section (for Apparatus type records) and to printed reports that list specifications.
    *** Version Information ***
    Reported: 5.1.24 Earliest: 0.0.0 Fixed: 6.0.19
  • The Hr/Unit cost for generic equipment (Inventory records with 'Generic Equipment' checked) is automatically applied to linked inventory (generic equipment added from the Inventory form Linked Inventory section of an equipment record). When the generic equipment record Hr/Unit value is changed, you are prompted to update all instances where the generic equipment is linked to equipment records.
    *** Version Information ***
    Reported: 5.1.24
  • Added a History section to the Vendor form, adding the ability to add vendor history records (with Date) to the vendor master file for tracking contracts, communication, etc.
    *** Version Information ***
    Reported: 5.4.45
  • When you change the Station value in an inventory record and there is linked inventory (generic equipment added from the Inventory form Linked Inventory section of an equipment record), you are prompted to update linked equipment record locations.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.0
  • Added auto-generated option for the Work Order # field in the Maintenance/Test Detail form and for the Training Course ID in the Training Class form. Auto-generate options are set from the Administrative Options form Database section Key Counters section.
    *** Version Information ***
    Reported: 5.3.24
  • Work Order Number is displayed in the Inventory form Maintenance/Test section in the Maintenance section. This column is located to the right and you will need to scroll to see it. You can move the Work Order # column by clicking and holding your left mouse button with the cursor on the Work Order # column header, drag the column to the left, then release the left mouse button. Right-click with the cursor in the Maintenance area and select the Save Configuration option to save the change.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.29
  • Enhanced Inventory record entry. Added 'Serial no' field validation, duplicate serial numbers are allowed but noted using soft validation.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.18
  • When you create a staff activity from the Maintenance form (open an apparatus go to Maintenance, add new maintenance item, put meter hours in then click on Staff activity under the Other tab). It defaults the hours from the Current meter reading in the Maintenace form rather than the duration field on the maintenance form. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.19
  • Enhanced distinct lookup code management. Distinct lookup codes are fields with allowable values based on entries made into that field. Added the ability to edit distinct values, so values that are invalid can be changed in one location and FH will make the change in each record that uses the value, or you can merge one distinct lookup value with another. Added the ability to combine values of one distinct lookup with the values of a different distinct lookup (for example, share the distinct lookup values for fire report 'equipment brand' with HazMat report 'equipment brand' values). Added additional administration controls to distinct lookups to limit values in distinct lookup fields to those included in list. Access to administrate distinct lookup values is controlled via user security. Once a distinct values for a lookup are finallized, you can lock the distinct value to only allow entries currently listed for the lookup.
    *** Version Information ***
    Reported: 5.2.18
  • Under Incident Type for the 611 code. Cancelled enroute is spelled:
    Canceled.
    Under Actions Taken it is spelled:
    Cancelled.
    Changed so both use the same spelling.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.19
  • When you type a partial street name, then Tab out of the field a lookup of street names is displayed. If you press New and then lookup Type, no values are listed. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.20
  • When you exceed 64,000 entries in the Streets lookup category, you get an error 31, invalid subcript reference at line 11 of proc/method lkp.olemultitree.insertelementitem and FH must be exited. This can happen for regional incident collection when 'Automatically add address components to the lookups from incident transaction files as needed' is enabled, or if streets are added via an import from external data. This problem has been fixed so that you are prompted about the 64,000 entry limit without requiring FH to be exited. An installable component that removes all streets is available for regional incident collection facilities that do not need to track streets.
    *** Version Information ***
    Reported: 5.4.98
  • The first time you view a map after a Longitude/Latiitude lookup, the map form just flashes and goes away. Maps are displayed after that. This problem has been fixed.
    *** Version Information ***
    Reported: 5.2.14
  • If you set up the pushpins via Workstation Options for the different property type and you print out the map for Occupancy Location you still get the Occupancy default instead of the pushpin. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.20
  • FH mapping is not accessible from Wildland Fire reports. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.33
  • Expanded daily reminders to display expired permits and staff birthdays.
    *** Version Information ***
    Reported: 5.0.81 Earliest: 0.0.0 Fixed: 6.0.27
  • Batch renew permits, creating new permits based on existing expired permits. Notes from the original permit can be carried over.
    *** Version Information ***
    Reported: 5.0.81
  • Added Hydrant Link Notes to the Hydrant Location form, accessed from the Occupancy record Additional Records section Hydrant Locations button.
    *** Version Information ***
    Reported: 5.0.81 Earliest: 0.0.0 Fixed: 6.0.33
  • Enhanced occupancy inspections allows new permits to be added or existing permits to be linked to the inspection record. Chemical inventory records can also now be linked to specific permits.
    *** Version Information ***
    Reported: 5.1.24 Earliest: 0.0.0 Fixed: 6.0.33
  • Added occupancy history records, for tracking historic changes to occupancy records like building modifications or name changes. Accessed from the Occupancy form Additional Records section Other History button.
    *** Version Information ***
    Reported: 5.2.41 X Earliest: 0.0.0 Fixed: 6.0.21
  • When a new inspection is autogenerated, the new inspection includes the end time from the previous inspection. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.38 Earliest: 0.0.0 Fixed: 6.0.0
  • Hide occupancies from lookups. From the Occupancy form, check 'Hide Occupancy in Lookups' to exclude the occupancy from browse queries when 'show hidden records' is unchecked.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.19
  • Enhanced import of violation code lookup table import makes creating inspection checklists based on violation code sets much easier. Accessed from the Checklist Items form Import from Violation Code Lookup Table button, check the specific violation groups and codes to create inspection checklist categories and items from, then pess OK. The existing items are overwritten with the selected groups and codes.
    *** Version Information ***
    Reported: 5.4.49
  • If an inspection checklist is created without any checklist categories, the checklist item(s) is not available on the PDA, or desktop when you select the use checklist button. This problem has been fixed. Categories are required in inspection checklists and the update will correct existing checklists.
    *** Version Information ***
    Reported: 5.4.49
  • Recalling an inspection template with responsible party information does not bring in the responsible party information. The responsible party information in the template is overwritten by the responsible party information associated with the occupancy record. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.64 Earliest: 0.0.0 Fixed: 6.0.44
  • Preplan record user fields. Allows for additional detail for preplans, for example, tracking sprinkler details. User-defined fields can be required based on the code value.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.22
  • Each checklist item in an inspection checklist should include an item description. When you add a checklist item to a specific category without an item description, the item is deleted. This problem has been fixed so that you are prompted that items without descriptions will be deleted.
    *** Version Information ***
    Reported: 5.4.8 Earliest: 0.0.0 Fixed: 6.0.18
  • Copy and install inspection checklists as FH components. Accessed from the Inspection Checklist form Options... button. See the FH help file 'Copy and Install Components' topic for additional information.
    *** Version Information ***
    Reported: 5.4.82
  • Added a Check Number field to the Inspection form.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.4
  • Added a 10 character Invoice Number field to the Inspection form. This field has a numeric auto-generate (Invoice# is not generated or enabled until the status is set to completed).
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.4
  • Enhanced Occupancy Management. New feature to merge occupancies. When merging, a second occupancy is selected and then you can select to merge the history of one occupancy to the other occupancy.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.45
  • Enhanced permit tracking. Simplified permit renewals by adding a Renew button to the Permits browse list. Highlight an expired permit and press Renew, then complete the displayed form to create a new permit. Added Batch Renew Permits option to the File menu Occupancy Management option to allow all expired permits to be renewed. You have the option to display only the newest permit during batch permit renewal. Also added the ability to associate multiple permit types to a single permit detail record. The fee of all associated permit types are summed in the Permit Billing Statement. Expired date is not required to allow for one-time permanent permits.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.26
  • When an inspection is marked as completed, even if there are no violations, you can enable a prompt to create the next scheduled inspection. This feature is enabled from the Administration menu>Administrative Options>Occupancy section>Inspection section 'When saving an inspection, prompt to create a future scheduled inspection' checkbox. You have additional options to only prompt when there are violations flagged for recheck, or to prompt whenever an inspection is completed.
    *** Version Information ***
    Reported: 5.4.74
  • Added a Number field to the Inspection form for numbering reinspections.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.4
  • When printing a violation notice when outstanding violations are identified in the first or second reinspection, you get an error 1581 Field Remarks does not accept null values at line 95 of procedure/method INSPECT.SAVE. This problem has been fixed.

    The fix is to make sure the Completed Date filled in and the status is set to completed.

    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.5
  • Previous FH versions allowed quotation marks and commas for lookup code Code fields. This problem has been fixed so that you are prompted when attemting to add a Code value that includes a comma or quotation mark.
    *** Version Information ***
    Reported: 5.4.95 Earliest: 0.0.0 Fixed: 6.0.22
  • Increased Title field length for Inspection Responsible Party records and Occupancy Contact records to 40 characters.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.17
  • Add a checklist item category without a description and save the inspection checklist, and the next time you open it you get:
    Error 4: End of file encountered. at line 27 of procedure/method FRMCHECKLISTITEMS.CTRGRDCATEGORIES.SEQUENCEDOWN. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.99
  • Enhanced occupancy contacts. Added a Date Out field that, when completed, can be used to limit contacts listed in the Occupancy form Owners & Contacts section. Added a Show field to the Occupancy form Owners & Contacts section that can be used to limit contacts to active contacts (no Date Out completed) or inactive contacts.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.48
  • Added occupancy history records for tracking occupancy changes (for example, building name changes). When enabled in administrative options (Administration menu>Administrative Options option>Occupancy section>Prompt to add history when name or building info changes checkbox), you are prompted to add an occupancy history record when saving an occupancy record with a changed occupancy name.
    *** Version Information ***
    Reported: 5.0.0 X Earliest: 0.0.0 Fixed: 6.0.20 0
  • Enhanced investigation narratives. Option to have narratives locked for non-administrative users and allow notes to be appended by any users. Enabled via the Administrative Options form Incident section All Incidents section by checking Only Allow Appending to Narratives (Not Edit).
    *** Version Information ***
    Reported: 5.4.55 X Earliest: 0.0.0 Fixed: 6.0.26
  • Enhanced date validation. Dates that appear to be invalid (for example, greater than 150 years in the past) are color-coded and you are prompted to verify the date.
    *** Version Information ***
    Reported: 5.4.8 X Earliest: 0.0.0 Fixed: 6.0.0
  • Installing FH Onsite Inspections does not update the PDAUPDATE.INI, and some issues may arise. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.40 Earliest: 0.0.0 Fixed: 6.0.16
  • Enhanced FH Onsite Inspections feature. Export incomplete inspections to FH Onsite Inspections directly from the Department Journal. Select the day with the inspection, press Options, then select 'Export Incomplete Inspections'.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.26
  • When an inspection uploaded to a PPC includes an inspector, but the staff member is not specifically selected for inclusion, the staff name for the inspector is not being included. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.21
  • Enhanced export from dock computer to FH Onsite Inspections assigns a unique ID to each export, preventing duplicate violations from being created.
    *** Version Information ***
    Reported: 5.4.98
  • When you attempt to import from the import folder into FH you get an Error 1541 Connection OCCUP is busy. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.10
  • Added an install selection option to install the PPC2003 and .net version of FH Onsite Inspections.
    *** Version Information ***
    Reported: 2.0.0 Earliest: 0.0.0 Fixed: 6.0.27
  • On import from the PDA the responsible party's city, state, and ZIP are being completed using the workstation default values even though they were not entered on the PDA. This problem has been fixed so that city/state/ZIP are not added to the responsible party record included on the dock computer (unless included from the PDA).
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.41
  • Default browse queries are definable at the workstation and/or user level for each query category. To set a default browse query at the workstation level, access the Queries form (Tools menu Queries option), highlight the query, press Default and select Set as Workstation Default.
    NOTE: The current system level default is still available, but you can override different defaults at the workstation level. When a workstation default is available, it is used even if a different global default is added for the category.
    *** Version Information ***
    Reported: 5.2.18 Earliest: 0.0.0 Fixed: 6.0.27
  • Added a query that lists only incidents (fire or EMS) with Mutual Aid provided.
    *** Version Information ***
    Reported: 5.1.24
  • Enhanced browse lists. Added additional formatting options to the Query Designer. Specify maximum width for certain types of output field (for example, Address() expressions). Set via the Query Designer form Fields section by selecting the output field, pressing Properties and checking Pad field width to. Also added the ability to modify browse lists displayed in the Query form. Click a column to change sort order, move or resize columns, and save these settings by pressing Options and selecting the Save Configuration option.
    *** Version Information ***
    Reported: 5.4.24
  • When certain queries are run, the cursor goes to the Details field and the query result list is scrolled to the right (making the query results appear to be empty). This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.47 Earliest: 0.0.0 Fixed: 6.0.44
  • Enhanced query filtering. Ignore Case is enabled by default when an upper-case only character field is selected and disabled by default for mixed-case character fields.
    *** Version Information ***
    Reported: 5.4.66
  • While running the 'Incident List by Street Name' report and adding the 'Street Number' to the Filter section, change 'Criteria' to 'Between' or to 'Inlist' then type two numbers, and the value changes when you tab out of the field. This problem has been fixed.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.19
  • Enhanced query security. User security is applied to all queries so that a user can not view any records they do not have security access to. For example, a user with access to the fire incident module only can add a staff member to an authorization record, but only the Staff ID is displayed in the staff browse list (staff first and last name will be masked since they do not have access to the staff area).
    *** Version Information ***
    Reported: 5.4.76 Earliest: 0.0.0 Fixed: 6.0.5
  • FH Enterprise only. In certain circumstances, printed report forms will return an error when a query name used by the printed report includes a numeral. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.82 Earliest: 0.0.0 Fixed: 6.0.34
  • When you add the FmtHours function from the Expression for Field on Report: form Advanced section, the FmtName function is inserted in the expression area. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.19
  • Enhanced record sorting. Sort Query from lists by any column. Double left-click column header to sort in ascending order (A to Z) or right-click to sort in descending order (Z to A).
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.15
  • Added the ability to show or exclude hidden records for all browse queries. Check the 'Show Hidden Records' checkbox at the bottom of the Query form to display records marked as hidden.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.22
  • In certain circumstances when you run a query and press "Add" without specifying an additional paramter, you will get an error. This problem has been fixed so that you are prompted to define the parameter before running the query.
    *** Version Information ***
    Reported: 5.4.98
  • While trying to create a new automated task to run a cross tab query you get an error stating 'No Columns Found' when setting up task parameters. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 5.3.24 Fixed: 6.0.19
  • A user with full rights to the Occupancy module can not add Checklist ID parameter criteria when running the Blank Inspection Checklist report. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.26
  • Added a graph that lists the number of Fire and EMS incidents for each month.
    *** Version Information ***
    Reported: 5.0.66
  • Added Daily Reminder Notes report.
    *** Version Information ***
    Reported: 5.0.67
  • Added hydrant contact reports that list hydrant contacts, owners, and purveyors.
    *** Version Information ***
    Reported: 5.1.24
  • Modified Transports by Final Destination reports (detail and summary) to include diverted to destinations if available.
    *** Version Information ***
    Reported: 5.3.24
  • When you print a violation notice and you have multiple scheduled inspections for that occupancy, the wrong 'recheck' date is listed on the violation notice. The first scheduled inspection is listed and most likely this is not the one that was just scheduled for this current inspection. Changed the behavior to get recheck date from scheduled inspections with the same violations as the current inspection. If there are none, The first scheduled inspection is listed.
    *** Version Information ***
    Reported: 5.3.24
  • Staff Member Participation Report now has a checkbox when setting report options for calculating participation of staff members listed as unavailable at the time of participation.
    *** Version Information ***
    Reported: 5.2.41
  • Enhanced programmed reports output options. Output program reports to graphical HTML, PDF, or other file types.
    *** Version Information ***
    Reported: 5.0.0
  • Added a new report to the collated batch NFIRS report that contains all the information from the NFIRS Incident Report>Additional Reports section>Dollar Loss & Value option.
    *** Version Information ***
    Reported: 5.4.47 Earliest: 0.0.0 Fixed: 6.0.4
  • The EMS Incident Report 'EMS Completion Status Report' does not print if the record is incomplete and there is no patient record. This problem has been fixed so that the completion status will print if the EMS incident is incomplete regardless of whether a patient record has been added.
    *** Version Information ***
    Reported: 5.4.47 Earliest: 0.0.0 Fixed: 6.0.0
  • Overhauled the 'Monthly Incident Counts By Station' printed report to run faster for large databases.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.33
  • If a report has a shared form (for example, the Hydrants by Location and Hydrants by Hydrant Number reports use the same shared form (HYD_0005)) and you copy one of the reports the copy is not created and editing the 'copy' of the report layout changes the original report form. This problem has been fixed in FH 6 so that copies are properly cre>ated.

    As a workaround in FH 5 you can access the system report properties form section and change to a Private Form instead of a Shared Form, then make a copy of the reports. After creating a copyy, access the system report again and change the form properties back to shared.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.41
  • In FH Enterprise, when you print a blank NFIRS 9 report you get Error 242:[Mircrosoft] [ODBC SQL Server Driver] [SQL Server] . This problem has been fixed.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.18
  • Enhanced HTML and PDF output, with options to email or FTP files directly to a specified location (e.g., a website) and improved graphical HTML formatting.
    *** Version Information ***
    Reported: 5.3.24
  • Added a new report that lists user-defined system rules/defaults values. Records are grouped and sorted by table. The table name is SYS_RULE, and the user-defined records in that table are the ones with FLAGS=1. This report was suggested at an FH Education & Training Seminar.
    *** Version Information ***
    Reported: 5.4.69 Earliest: 0.0.0 Fixed: 6.0.52
  • Total participation on the YTD Participation report of 100% participation is displayed as "****". This problem has been fixed.

    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.5
  • Rearranged Staff Participation Report form, adding a separate area for specifying staff members.
    *** Version Information ***
    Reported: 5.3.41
  • The Hydrant Flow Test by Hydrant query is missing the field hyd_main.addr_2 field. This problem has been fixed, and the layout of the report was cleaned up to align columns.
    *** Version Information ***
    Reported: 5.4.79
  • When the Hydrant Flow on the Flow test is over 1,000 and you run the Hydrant by Location (summary) report it is displayed as "***." This problem has been fixed by changing the format from 999 to 9999.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.0
  • Missing/Unused Incident Numbers with Count. Includes an annual total count of missing/unused incident numbers for the year.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.6
  • If you try to print the reminders and have Departmental events set up for the future the event does not show the Event code under the description. This problem has been fixed.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.0
  • The description included in the Advanced Function Detail form is obsolete. It has been updated.
    *** Version Information ***
    Reported: 5.4.81
  • The Average Reaction, Highest Reaction and Lowest Reaction is using the same calculation as the Average Response, Highest Response and Lowest Respone in the report Unit Response by Incident is printing. This problem has been fixed.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.5
  • If a report is printed from a data entry form, and there is no default printed report for that form or the user selects the "Select Report to Print..." option, and the selected report is outside the category of the data entry form (e.g. an incident report is run from the occupancy form) - the report results may come up with 'There are no records in the main query for this report." When reports are run from data entry, parameter values are assumed based on the record displayed on the data entry form. These values become "default" parameters. This problem has been fixed so that when a report is run outside the intended category, parameter values are not assumed unless they are relevant.
    *** Version Information ***
    Reported: 5.4.84
  • Running a report with 'Having' statements and attempting to filter using the Having section from the Query Parameters form can cause a 1526 Connectivity Error when custom expressions are used in the Having section. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.82
  • Part 3, Line 19 and 25 of the NFPA fire experience survey report is not totalling correctly. Line 19 and 25 need to have line 13 added to the equation as well. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.82
  • If you go to reports, then EMS Patient report and run the Incident Report the scene narrative only prints for the 1st incident over and over. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.89 Earliest: 0.0.0 Fixed: 6.0.4
  • Enhanced Department Journal report. Include notes in details. Detail report lists total number of staff for each activity and the total staff hours. The counts by type as well as total for record (e.g., for an incident or activity, you would list subtotals for each activity code for the activities for that incident. For training it would be the individual training category totals (count and hours)). *** Version Information ***
    Reported: 5.4.89 Earliest: 0.0.0 Fixed: 6.0.20
  • The YTD Participation Report does not show EMS runs. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.80 Earliest: 0.0.0 Fixed: 6.0.4
  • The Inventory Detail by Description report misspells "Recieved". This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.0
  • Enhanced LastHydrFlow function to display or exclude specific hydrant activity types. See the FH Help File 'LastHydrFlow' topic for additional information.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.37
  • LOSAP report enhancements. Added the Suffix (Jr, Sr, III and etc.) to staff name in the report layout. The total number of incidents, training and activities that were available during the date/time frame are shown. The summary report includes maximums on all pages of the report so the totals can be easily compared.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.10
  • The Fire Incident Cost (Manpower & Vehicles) report calculates staff members time and cost for units for each incident and related exposure. This problem has been fixed so that staff member time and unit costs are only calculated once for an incident with exposures using values from base incident.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.10
  • Hydrant Activities by Staff report swaps check boxes for painted and serviced hydrants in the report layout. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98
  • The group by for activity information is set for act_main.act code but the training information is grouped by trn_det.trn code in the Department Activity Report. Entering multiple activity detail records into a single activity main record causes a misrepresentation of the data. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.12
  • If you are running the LOSAP summary report and you have the percent side set up say 0-10% gives 1 point, 11-20% gives 2, etc and you only run it selecting a single staff member the points are not calculating at all. If a person has 8% they should get 1 point, they are showing no points. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.14
  • When you create a new report, and choose to make copy of the LOSAP report, it does not generate new copies of both detail and summary forms. When the layout for the summary form is modified, both the original and copy of report layouts are modified. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98
  • Added a printed 'Database Detail Audit History by Record" report that includes all the detail of all the child table records.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.43
  • When you have no agency associated with an arson investigation a phone number is appearing when printing the NFIRS - 11 Arson Page 1. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.99 Earliest: 0.0.0 Fixed: 6.0.20
  • Access the Administrative Options form Staff section and press Setup LOSAP Values and a beginning date (the first of this calendar year) and an end date (the date it was modified, i.e. today) is defaulted. This problem has been fixed.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.14
  • Certain multiple-part printed report forms (for example, NFIRS forms) do not print front and back, a blank page is inserted between the end of one report and the start of the other in certain circumstances. This problem has been fixed so that multiple part forms will print front to back without blank pages unless blank pages are specified in the report layout.

    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.37
  • When you run the LOSAP report and specify a % range for an item and the items does not occur in the results, you get an Error 39: Numeric Overflow. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.82
  • Some printed report forms return a 1526 error when certain values are included in address fields. Characters in the street number field, which is numeric, cause the error (e.g., 14A or 31-2). This effects a number of reports including the Incident List by Street Address, Hydrant Check List by Location, and Hydrant Field Cards (4"x6") reports.
    *** Version Information ***
    Reported: 5.4.98
  • FH installable component names do not allow quotation marks (") in the component name. This problem has been fixed so that FH6 installable files with quotations in their names can be created and imported.
    *** Version Information ***
    Reported: 5.4.98
  • The Structure Fire Report includes some incosistencies, including alignment and various sized 'X's. This problem has been fixed.
    *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.20 E
  • When printing the Permit Application report under Occupancy Blank forms it prints a page for every occupancy in the database. If there are 1200 Occup ID's entered it will print 1200 pages. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.26
  • If you have a report with multiple layout files for the same query, (Staff Participation for example) and you attempt to output the report to PDF and it is not the first (usually detail report) form, then it goes right to the printer and does not create a PDF file. If you attempt to output the summary or concise summary participation report to PDF it sends it to the printer, if you do the same thing with the detail it will work. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.26
  • The 'Default Hrs Pd' value is not calculating correctly for the group footer for each class for the Training Classes by Category report. This problem has been fixed.

    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.20
  • Programmed reports added as automated tasks (e.g., LOSAP) are not keeping parameter values set up for the task. Also, you might get 'Error 1234: Subscript is outside defined range'. This problem has been fixed.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.50
  • The Apt/Room/Suite value from occupancies is not included in the occupancy address included in many printed occupancy reports (for example, the Violation Notice). This problem has been fixed so occupancy apartment/room/suite values are included in occupancy printed reports.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.50
  • The Apparatus Inventory Checklist report needs more space to print Inventory ID's longer then 13 characters and the
    Eqpt_ID box in detail band needs to be made wider. These issues have been fixed.
    *** Version Information ***
    Reported: 5.5.10 Earliest: 0.0.0 Fixed: 6.0.55
  • Inventory Detail by Description report, Recieved Date should be spelled 'received'. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.58
  • When you run the shift calendar and you have not set up a default shift calendar or you specify an invalid shift in parameters you get an Error 31: Invalid subscript reference. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.48 Earliest: 0.0.0 Fixed: 6.0.5
  • Added the ability to disable Assigned Staff requirement for exchanges. Check the Schedule Personnel Exchange form 'This is additional staff, not an actual replacement' checkbox if an off duty staff member needs to be added to a schedule (for example, to cover a special event).
    *** Version Information ***
    Reported: 5.4.76 Earliest: 0.0.0 Fixed: 6.0.20
  • Staff Scheduling improperly allows an end date/time in the exchange that is earlier than the start date/time. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.81 Earliest: 0.0.0 Fixed: 6.0.2
  • Added Scheduling Control Panel. The Scheduling Control Panel provides complete control of Staff Schedule records. The Scheduling Control Panel displays working staff and all involved staff added for the selected schedule in a drill-down list grouped by station then unit. Drill down through the station and the unit to see staff for that station and unit.

    Staff can be dragged from one unit to another unit to create an exchange record for this staff member as the assigned and replacement, for the entire shift. The activity detail defaults are left as they were before this staff was moved except the station and unit are changed to the station and unit the staff was moved to. The exchange record is displayed so the defaults can be modified if need be.
    *** Version Information ***
    Reported: 5.4.84 Earliest: 0.0.0 Fixed: 6.0.20
  • Staff Scheduling is an optional module in FH that can be evaluated by current clients. In certain scenarios, administrative settings set during the evaluation remain active after the evaluation expires, disabling Station Roster and affecting calendar form display. This problem has been fixed so the Staff Scheduling administrative options that effect FH are disabled when the evaluation expires.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.6
  • Several times fields display afternoon times in 12 hour format instead of 24 hour time format (e.g., 05:30:00PM instead of 17:30:00). This problem has been fixed so that times are displayed in the same format as elsewhere in FH.
    *** Version Information ***
    Reported: 5.4.95 Earliest: 0.0.0 Fixed: 6.0.5
  • When an exchange is added with no replacement, and you specify Hours Worked and Hours Paid for the exchange record, the specified values are not added to the activity created from scheduling. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.95 Earliest: 0.0.0 Fixed: 6.0.51
  • Added Request Date and Approval Dates to exchange records to track when an exchange was first requested and when the exchange was approved.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.20
  • Added the ability to add an exchange for and individual for extended leave, generating an exchange for each day the staff member works for the duration of the specified period. To add extended leave, from the Scheduling Console, press Extended Leave and enter details about the staff member extended leave.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.0
  • Create/Edit Activity from scheduling, then cancel or save, then press Transfer to Roster button and no units are listed. The interface has been changed and this problem no longer exists.

    *** Version Information ***
    Reported: 5.4.0 Earliest: 0.0.0 Fixed: 6.0.33
  • The Approved By field in scheduling forms (e.g., exchanges) is not including any lookup options other than the current use unless real-time links is enabled. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.14
  • Mass exchange approval. In the Scheduling Control Panel form, you can select multiple unnapproved exchanges, press Approve Exchanges, enter an Approved By value and press OK to approve all exchanges at one time.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.33
  • Modified the Station Roster & Availability form to prevent changes when real-time links to the station roster are enabled via the Workstation Options form Scheduling section.
    *** Version Information ***
    Reported: 5.4.98
  • Shift Calendar Report splits shift names improperly when multiple shifts are included for a day and the shift names do not include spaces. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.21
  • New functions for current shift on duty and current staff on duty.

    CurrentShiftCode(tWhen, cSched_id)
    Both parameters default appropriately so the common is CurrentShiftCode().

    CurrentStaff(tWhen, cSched_ID, cExpr)
    Parameters are similiar to ListDetail().
    *** Version Information ***
    Reported: 5.4.98
  • Enhanced scheduling. When 'Real time link with data entry is enabled via the Workstation Options form Scheduling section, selecting a staff for an authorization record from scheduling inserts the staff name and updated the Rank field in the authorization record.
    *** Version Information ***
    Reported: 5.5.10 Earliest: 0.0.0 Fixed: 6.0.38
  • In certain circumstances, when you create a staff activity from a schedule for a date with multiple shifts on duty at the same time, then view another day's schedule, only staff from the last shift active for the date the activity was created for are displayed. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98
  • Events that end on a date boundary are no longer displayed in the ending day on the Department Journal. For example, if a staff activity goes from 8/12/2003 at 22:00 to 00:00 of 08/13/2003 the icon for the activity will not be displayed in 08/13/2003.
    *** Version Information ***
    Reported: 5.3.24 X Earliest: 0.0.0 Fixed: 6.0.44
  • Added notes field to Pay Rate Detail form.
    *** Version Information ***
    Reported: 3.0.0 X Earliest: 0.0.0 Fixed: 6.0.21
  • Increased the width of the Training Category Code field to to 12 characters.
    *** Version Information ***
    Reported: 5.0.66
  • Enhanced staff history records with additional security and the ability to add user-defined fields and attach files. Add Staff History records then check 'Viewable Only By Staff Administrator' to restrict viewing to administrative access users.
    *** Version Information ***
    Reported: 5.1.12
  • Hidden staff members are automatically excluded from staff lists in the Training Program form Staff Members section and the Update Expired Certification forms. A Show Hidden Staff Members checkbox is available if 'Hidden' staff members need to be listed.
    *** Version Information ***
    Reported: 5.2.26
  • Enhanced process of associating equipment with staff members. From the Staff form Additional Records section, press Equipment and when no equipment has been added for the staff, a browse list for selecting existing inventory records is displayed. Select inventory (you can select multiple records) and press OK to associate record(s) with staff member, or press Cancel and then New to add a new inventory record.
    *** Version Information ***
    Reported: 5.2.36
  • Expanded staff administrative records, with a new EMS Certification Expires date field.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.18
  • Enhanced staff history records with additional security and the ability to add user-defined fields and attach files. Add Staff History records then check 'Viewable Only By Staff Administrator' to restrict viewing to administrative access users.
    *** Version Information ***
    Reported: 5.0.0 X Earliest: 0.0.0 Fixed: 6.0.18
  • Enhanced Training Class Details. Add multiple Training Category codes for a single training class participant. Added via the Attendee Detail form using the "+" or "++" buttons at the bottom of the form.
    *** Version Information ***
    Reported: 5.4.39 Earliest: 0.0.0 Fixed: 6.0.49
  • Expanded Staff History records, with the ability to add user-defined fields and attach files.
    *** Version Information ***
    Reported: 5.3.24 Earliest: 0.0.0 Fixed: 6.0.18
  • Add equipment usage records from Staff Activity and Training Class records. Accessed from the 'Other...' section 'Equipment Used...' button.
    *** Version Information ***
    Reported: 5.3.0 Earliest: 0.0.0 Fixed: 6.0.18
  • Enhanced Years of Service calculations. Added an End Service Date field to the Staff form. When an End Service Date value is added, Years of Service is calculated using the elapsed time from Hire Date (Adjusted Hire Date if available) to End Service Date. *** Version Information ***
    Reported: 5.4.82
  • Add staff casualty reports from Staff Activity records and Training records. Accessed via the Other section Casualty Reports button. *** Version Information ***
    Reported: 5.0.0 Earliest: 0.0.0 Fixed: 6.0.16
  • Added a Notes field to the Pay Rate Detail form. Accessed from Staff form>Additional Records section>Administrative button>Pay Rates button.
    *** Version Information ***
    Reported: 5.4.98
  • Adding groups for staff activities was validating inconsistently depending on certain conditions. Modified group add functionality to add participant details giving precedence to system rules and default values. Validation is performed when the activity record is saved.
    *** Version Information ***
    Reported: 5.4.96 Earliest: 0.0.0 Fixed: 6.0.26
  • When you select staff from the Staff Master list or Saved Groups with a large list of members using the scroll wheel on the mouse, there is a refresh issue that makes it appear that the selected members have disappeared. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.29
  • Added 'Other Stations' area to Staff form for adding all stations staff member will respond from. When adding groups of staff to records (for example, Staff Activity records) staff will be included in the station-specific lists of each station added for their records.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.18
  • Renumbering a Staff Schedule record that is also the default schedule indicated in Workstation Options does not change the ID number. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.37
  • When you start a new training class and use today's date and press Add the attendance status defaults to 'Scheduled' instead of 'Attended'. This problem has been fixed and 'Scheduled' will only default if the training date is greater than today's date.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.26
  • Added the ability to overwrite the default value in the Attendance status field in the Staff Activity Detail. By default, "Attended" is assumed if the activity Start Date is less than the current date, and "Scheduled" if the Start Date is greater than the system date. *** Version Information ***
    Reported: 5.5.10 Earliest: 0.0.0 Fixed: 6.0.41
  • The Lookup databases are generally located in the Database directory. Previous FH versions allowed the Lookups database to be stored locally, but the need for local Lookup databases was replaced with local caching. FH still allows a separate Lookup for backward compatibility, but FH directory listings explicitly illustrate the default Lookup database location.
    *** Version Information ***
    Reported: 5.1.0 X Earliest: 0.0.0 Fixed: 6.0.19
  • Expanded 'Table Name' column in the Duplicate Table Found form to allow the entire path to be displayed.
    *** Version Information ***
    Reported: 5.4.81
  • Except in special instances, Lookup tables are located in the Database directory, but the FH update utility tracks their location independently. The update utility has been modified to automatically default the Lookup database location when lookup tables are detected in the Database directory.
    *** Version Information ***
    Reported: 5.4.0 Earliest: 0.0.0 Fixed: 6.0.19
  • During update, when "Data" is updated and "Lookups" is deselected, lookup data tables could be deleted during an update. This problem has been fixed so that files are not deleted, and a backup of current files is created. The update creates updated files and overwrites files as needed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.26
  • After an update where you opt to keep modified queries and reports, system reports are linked to the modified queries. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98 Earliest: 0.0.0 Fixed: 6.0.19
  • When running the update on a database with statistics enabled, the update errors when creating indexes. This problem has been fixed.
    *** Version Information ***
    Reported: 5.4.98