7.16.07 Release Notes

FH Enterprise and FH Web now support SQL Server 2012 databases.

Warning: You must update to FH 7.16.07 prior to using SQL Server 2012. After updating FH, you can then move your FH database to SQL Server 2012.

Once the FH database is moved to SQL Server 2012, future updates to FH occur in the SQL Server 2012 database.

The following NEMSIS files have been updated on the FH installation CD in the State directory, and on the Firehouse web site.

Caution: After updating FH, you must launch FH and log into it for FH to perform the automatic update of the NEMSIS files.

• NemsisID.FHz
• NemsisID2.FHz
• NemsisGA2.FHz
• NemsisVA2.FHz
• NemsisOH2.FHz
• NemsisSD.FHz
• NemsisSD2.FHz
• NemsisAK2.FHz
• NemsisOK.FHz
• NemsisOK2.FHz
• FLDemographicExport

The following files contain the current listing of hospitals for the state, and can be downloaded from the FH web site.

• IDHosp.FHz
• GAHosp.FHz
• VAHosp.FHz
• OHHosp.FHz
• MOHosp.FHz
• AKHosp.FHz

You now have the administration option to disable the Rating Bureau tab in the Training Class dialog box, and you can disable an individual rating bureau class criteria.

To find the new interface elements related to the feature additions, do the following.

1. Choose Administration → Administrative Options.

2. In the Administrative Options dialog box that appears, click the Staff tab, and then the Activities & Training sub-tab.

   At the bottom of the tab, in the Rating Bureau section, the Disable rating bureau criteria tab (overrides individual code requirements) option appears. If you select this option, in the Training Class dialog box, the Rating Bureau tab is disabled.

   

3. Click OK.
4. Choose Tools →Lookup Tables.
5. In the Lookup Tables dialog box that appears, expand Staff Activity and Training Codes → Training Class, Program, and Instructor Codes.
6. Select Rating Bureau Criteria, and then click Setup.

7. In the Lookup - Rating Bureau Criteria dialog box that appears, select a lookup code, and then click Edit.

   In the Code for Rating Bureau Criteria dialog box that appears, in the lower left corner of the dialog box, the Disable this code option appears. If you select this option, and save the change, the corresponding row for the criteria in the Training Class dialog box, on the Rating Bureau tab, becomes disabled.

   

If you entered data into the module containing user fields, then opened the user fields portion of the module with the steps below, the data entered since your last save might not be saved.

1. Open or create a record in a module that has user fields defined for it, and enter data as normal.
2. Without clicking Save in the module dialog box, click the Other tab.

3. Click User Fields.

   The User Fields dialog box for that module appears.

4. (Optional) Enter data in the user fields as normal.
5. Close the User Fields dialog box.
6. In the module dialog box, click Save, and then click Close.

7. Reopen the record you just closed.

   Any data you had not save before clicking User Fields might not be saved in the module record.

If you are using the NEMSIS lookup codes and you updated to FH 7.16.06, then entered patient data in the EMS module with the steps below, the patient narrative and three fields on the Status & Transport tab did not save as expected.

1. Update to FH 7.16.06.

2. Log into FH and create a new EMS record as normal.

   The EMS/Search & Rescue Report dialog box appears.

3. Click the Patients/Victims tab.

4. Click Add to add a new patient/victim record.

   The Patient/Victim Information dialog box appears.

5. Fill in the patient record as normal, being sure to specify the following information:

   • On the Status & Transport tab, specify data for the Patient Status, Initial Destination/Facility Code, and Destination Determined By fields.
   • On the Patient Narrative tab, enter a patient description of the incident.
6. In the Patient/Victim Information dialog box, click Save, and then click Close.

7. In the EMS/Search & Rescue Report dialog box, select the patient/victim record you just saved and closed, and then click Open.

   Data entered in the Patient Status, Initial Destination/Facility Code, and Destination Determined By fields did not save, and the fields are empty.

If you tried to propagate ODBC connection information with the following steps, the information did not propagate to the selected workstations as expected.

1. Choose Tools → Wizards → Workstation Settings Deployment Wizard.

   The Workstation Settings Deployment Wizard dialog box appeared.

2. Expand Remote Access Configuration, and then select ODBC Connection Options.

3. Click Next >.

   The next screen of the wizard appeared.

4. Select the workstations you want to propagate the ODBC connection information to, and then click Next >.

   The summary screen of the wizard appears.

5. Click Finish.

   The ODBC connection information did not propagate to the selected workstations as expected.

Note: The ODBC Connection Options is no longer supported, and has been removed from the Workstation Settings Deployment Wizard dialog box in this release.

If you tried to send data in the FH database to a printer from a number of different places in FH, after selecting the printer you want, the following error message appeared, and the print job was not sent to the printer.

"The selected printer is not ready, Please confirm that the printer is connected to your computer and that it is online. Select "Retry" to try again or "Cancel" to abort the attempt.

In FH Inspector, if you entered general notes while doing a reinspection, with the steps below, the notes were not sent back to the FH database during the synchronization process between the FH Inspector and FH.

In an incident report, if you reported the number of acres burned as none with the steps below, and then exported a NFIRS report, the incident report was rejected as invalid by the state fire marshal's office.

1. Begin a new incident record with a fire, or open an existing incident record with a fire, as normal.
2. In the NFIRS Incident Report dialog box, click the Additional Reports tab.

3. Click Fire.

   The Fire Report dialog box appeared.

4. Under Acres Burned, select None.
5. Under Acres Burned, leave the field for the number of acres blank.
6. Click Save.
7. Fill out the rest of the incident report as normal.

8. Export the NFIRS report and submit it to the state fire marshal's office as normal.

   The exported incident report left the number of acres field blank, and this was rejected as invalid by the state fire marshal's office.

If you tried to save an inventory maintenance record with the following steps, FH locked up.

1. Begin a new inventory record for an apparatus, or open an existing inventory record for an apparatus, as normal.
2. In the Inventory dialog box, click the Maintenance/Test tab.
3. Under Maintenance, add a new maintenance record, or open an existing maintenance record, as normal.
4. In the Maintenance/Test Detail dialog box that appears, on the Basic tab, fill in fields as normal.
5. Click the Notes tab.

6. Enter some text, and then click Save.

   FH locks up.

If the computer you are installing FH on does not have the FH prerequiste of MS .NET Framework 2.0 already installed, the installation stops with the following message.

"Windows cannot find 'C:\Windows\micos~1\framew~1\V2.0.50727\regASM.exe' Make sure you typed the name correctly, and then try again. To search for a file, click on the Start button, and then click on Search."

If you searched for an occupancy whose record contained an apostrophe (') with the steps below, the following error message appeared.

Error 36: Command contains unrecognized phrase/keyword. at line 33 of procedure/method FRMGRIDFIND.FIND.

1. Begin a new occupancy record , or open an existing occupancy record, as normal.
2. Click Browse.
3. In the Query dialog box that appears,click the find icon .

4. In the Find in Grid dialog box that appears, in For Text, type text containing an apostrophe.

   Example: O'Reillys

   The error message appeared.

If you tried to filter out (hide) the display of expired permits in a day journal view with the steps below, the expired permit information remained displayed.

1. Choose Tools → Workstation Options.
2. In the Workstation Options dialog box that appears, click the Other tab, and then click the Journal & Reminders sub-tab.
3. Select Use Day Journal instead of Month Journal (May perform better for larger departments).
4. Click OK.
5. Open the Department Journal as normal.
6. In the left pane, select a date that has an expired permit associated with it.

7. In the left pane, below the calendar, click the Expired Permits icon as needed to filter out (hide) the display of expired permits.

   The expired permits information remained displayed, regardless of the filter setting.

If you established an ODBC data source connection to a data source on the computer as normal, when you tried to log into FH Enterprise, the following error message appears.

Error 911: [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'From ODBC' does not exist. Make sure that the name is entered correctly.

If you tried to access the right-click menu for staff members in a training program with the steps below, the following error message appeared.

Error 2199: Error building key for index "c:\users\11057474\appdata\local\temp\000dhus901hw.cdx" tag "Sortcol". at line 106 of procedure/method CERTCODE.PGFDATA.PAGE2.CTRGRDROSTAFF.GRDMAIN.INDEXCOLUMN.

1. Open an existing training program record, as normal.
2. In the Training Program dialog box that appears, click the Staff Members tab.

3. Right-click the label of the Name column.

   The error message appeared.

If you try to access a report layout's data environment with the steps below, the Data Environment dialog box did not appear as expected.

1. Choose Reports → report type option.
2. In the Reports dialog box that appears, select the report that you want to work with, and then click Layout.
3. Respond to any prompts about making a copy of the selected report or modifying the selected report as appropriate.
4. In the prompt dialog box for specifying uery parameter value for layout preview data, respond to any prompts as appropriate.

5. In the Report Designer dialog box that appears, in any blank area in the dialog box, right-click and then choose Data Environment.

   A small box flashes up on the screen and then disappears, no error appeared, and the Data Environment dialog box did not appear.

If you try to run two custom data exports in a row with the steps below, the second export does not run.

1. Choose Administration → Database Administration → Custom Data Export.
2. In the Custom Data Export dialog box that appears, select and run an export as normal.

3. In the Custom Data Export dialog box, select a different export and try to run it.

   The export does not run as expected.

   Note: If you closed the Custom Data Export dialog box and repeated steps 1 and 2, you could run the second export as normal.

If you link an accounts receivable inspection to an inspection with the steps below, FH enters an infinite loop and does not link the account to the inspection.

1. Open an existing occupancy record as normal.
2. In the Occupancy dialog box that appears, click the Inspections & Activities tab.
3. Under Completed Inspections, select an inspection, and then click Open.
4. In the Inspection dialog box that appears, click the Other tab.
5. Click Linked Account.
6. In the Account Link dialog box that appears, select Create or change the link to an existing account, and then click OK.
7. In the Query dialog box that appears, select the account to link to, and then click OK.

8. In the Account Link dialog box that reappears, select Create or change the link to an existing account, and then click OK.

   The Account Link dialog box reappears, and regardless of how many times you click OK, the account is never linked with the inspection.

If you enabled detailed audit tracking and the ability to track changes to field, and made changes to a patient record with the steps below, users without the appropriate permissions were able to view the changes in the incident record.

1. Enable audit tracking and field change tracking.

   1. Choose Administration → Administrative Options.
   2. In the Administrative Options dialog box that appears, click the Database tab, and then click the Auditing sub-tab.
   3. Select Enable detailed audit tracking.
   4. Select Track Changes to fields.
   5. Click OK.
2. Change a patient record.

   1. Open an EMS record as normal.
   2. In the EMS/Search & Rescue Report dialog box that appears, click the Patients/Victims tab.
   3. Open a patient/victim record as normal.
   4. Make changes to the patient record.
   5. Click Save, and then click Close.
   6. In the EMS/Search & Rescue Report dialog box, click Save, and then click Close.
3. View the changes in the incident record.

   1. Open the incident record related to the EMS record you modified, as normal.
   2. Click the Other tab.
   3. Click Record Modification History.

   4. In the Record Modification History dialog box that appears, click the Changes tab.

      The changed information is listed, even to users who do not have permissions to view the data.

If you begin an incident record, add an EMS report, and try to select the staff member who took exposure precautions with a patient using the steps below, and if you have a long list of staff members to select from, the list may be longer than can be displayed on your monitor, and no scroll bar exists to move up and down the list.

1. In the NFIRS Incident Report dialog box that appears, click the Additional Reports tab.
2. Click EMS/Search & Rescue.
3. In the EMS/Search & Rescue Report dialog box that appears, click the Patients/Victims tab.
4. Under the Patients/Victims list, click Add.
5. In the Patient/Victim Information dialog box that appears, click the Clinical tab, and then click the Provider sub-tab.
6. Under Exposure Precautions Taken, select Yes.
7. In the Exposure Precautions dialog box that appears, click Add.

8. In the Exposure Precaution Detail dialog box that appears, for Staff ID, click the lookup button.

   A pop-up menu of staff members appears. If the menu of staff members is longer than can be displayed on your monitor and not see the staff member you want to select, you are not able to scroll up or down the list to find the staff member.

If you renumber staff member IDs with the steps below, scheduling exchanges between staff members become unapproved, and the information concerning which staff member approved the exchanges is no longer accurate.

1. For each staff member whose ID number needs to be changed, do the following.

   1. Open a staff member's record as normal, so that the Staff dialog box appears.
   2. Choose Form → Renumber Staff.

   3. In the Renumber - Staff Members dialog box that appears, in Enter the new Staff ID value, type a new ID number for the individual, and then click OK.

      The Renumber - Staff Members dialog box closes, and in the Staff dialog box, the value in Staff ID updates.

   4. Click Save, then Close.
2. Open the Scheduling module as normal.

3. Open an existing approved staff exchange record between two of the staff members whose ID number has been updated, as normal.

   The previous approval recorded on the exchange record is gone (the exchange is no longer approved). The Approved By field still shows the old staff ID, but no name.

If you try to run two external data imports in a row with the steps below, the second export does not run.

1. Choose Administration → Database Administration → Import from External Data Source.
2. In the External Data Imports dialog box which appears, select and run a data import as normal.

3. In the External Data Imports dialog box, select a different import and try to run it.

   The import does not run as expected, and you are also not able to modify another import.

   Note: If you closed the External Data Imports dialog box and repeated steps 1 and 2, you could run or modify the second import as normal.

If you opened a new drawing with FH Sketch or tried to modify an existing drawing with the steps below, a For Evaluation Purposes Only message appeared.

1. Open an occupancy record as normal.
2. In the Occupancy dialog box that appears, click the FH Sketch tab.

3. Click either New Sketch, or select a sketch name and click Open Sketch.

   A For Evaluation Purposes Only message appeared in the area where a sketch thumbnail image would normally appear, and an Apex Registration dialog box appears, stating that this copy of Apex is not registered.

If you established an ODBC data source connection with FH Enterprise using the steps below, the password for the SQL Server login credentials is not saved as expected.

1. Choose Start → All Programs → FIREHOUSE Software version number → FIREHOUSE Software Enterprise Edition Tools → Remote Connection Configuration.

   The Remote Configuration dialog box appeared.

2. Under Connect Using, select ODBC Data Source.

   The options in the dialog box update to reflect your choice.

3. Specify the ODBC date source name and default database as normal.
4. Click the Login tab.
5. Clear Use Windows NT Authentication.
6. Specify the SQL Server login credentials, as normal.
7. Select Remember Password.

8. Click OK.

   The password is not saved for future logins as expected.

If you open a report from the Department Journal and then try to print it with the steps below, the following error message appeared.

Unable to open user field table 'XXXX' in exclusive access mode. Exclusive access to this table is require to make modification to user field definitions.

1. Open the Department Journal as normal.
2. Select a date that has a report containing custom user fields.
3. In the list on the right, select the report with the customer user fields, and then at the bottom of the list, click Edit.
4. In the module dialog box that appears, in the lower right corner of the dialog box, right-click Print.

5. In the Output Report To dialog box that appears, select the options to send the output to a printer as normal, and then click OK.

   The error message appeared.

Even if you set administration options that let end users view their own staff record with the steps below, the end user is not able to print information from their record.

1. Log into FH as an administrator, and do the following.

   1. Choose Administration → Administrative Options.
   2. In the Administrative Options dialog box that appears, click the Staff tab, and then click the General tab.
   3. Select Allow all staff read-only access to their own staff records.
   4. Click the Database tab, and then click the Data Security sub-tab.
   5. Select Respect View Security and Privacy in Queries, Reports, Graphs, and Maps.
   6. Click OK.
   7. Log out of FH.
2. Log in to FH as a user without administration privileges.

3. Open your own staff member record, as normal.

   In the Staff dialog box that appears, you could view your own staff record, but could not print it.

If you create a conditionally required system rule on the Role(s) field in the incident record with the steps below, the rule is not implemented.

1. Define the conditional requirement rule on the Role(s) field.

   1. Choose Administration → System Rules and Default Values.
   2. In the System Rules and Default Values dialog box that appears, expand Activity, and then select Staff Activity Participants.
   3. Click Setup.
   4. In the next System Rules and Default Values dialog box that appears, select ROLES, and then click Add.
   5. In the Select Rule Type dialog box that appears, select Require Field and then click OK.
   6. In the Require Fields dialog box that appears, clear Require field always.
   7. In Require field when the following expression evaluates to true, type
      INLIST(Incidentrecord.Inci_type,"111","113")
   8. Click OK.
   9. In the System Rules and Default Values dialog box, click OK.
   10. In the initial System Rules and Default Values dialog box, click Close.
2. Begin a new incident record as normal.
3. In the NFIRS Incident Report dialog box that appears, on the Basic tab, for Incident Type, select either the 111 or 113 lookup code.
4. Click the Units & Personnel tab.

5. Under Personnel, click Add.

   In the Participant Details dialog box, the Role(s) field is not highlighted in yellow to indicate that it is a required field, as expected. When you click Save in the dialog box, the Validation Results dialog box that appears does not contain a message indicating that Role(s) is a required entry.

If you imported data from a fire station into FH with the steps below, an error message appeared.

Error updating Audit Record Save/Delete History for module name.

1. Choose File → Station Management → Import Data from Station.

2. Use the Import Data from Station dialog box that appears to import an appropriate data file, as normal.

   The error message appears, and the import data from station log is not updated any details to confirm whether or not the data actually got imported. However, the data was imported.

If you add a staff member to the personnel roster with the steps below, the following error message appeared.

Error 18: Line is too long. at line 133 of procedure/method ROSTER.DBSESSION.VIEWOPEN.

1. Choose File → Station Management → Station Roster & Availability.
2. In the Station Roster & Availability dialog box that appears, click the Personnel Roster tab.
3. Double-click the Name label at the top of the Name column to sort the personnel list by alphabetical order.
4. Click Add.
5. In the Station Roster dialog box that appears, for Staff ID, click the lookup button and add select a staff member to add to the personnel roster as normal.

6. Click Save.

   The error message appeared.

If you create a new query for staff records with the steps below, the Staff ID column of the results returned is blank.

1. Create a new staff record as normal.
2. In the Staff dialog box that appears, in the lower right corner, click Browse.
3. In the Query dialog box that appears, click New Query.
4. When the prompt to start by making a copy of an existing query appears, click No.

5. In the Query Designer dialog box that appears, create the staff query as normal.

   Note: Make sure that the sft_main.Staff_id field is one of the output fields for the query.

6. Click Save, and then click Close.

7. In the Query dialog box, from Select a Query, select the new query you created.

   The query results in the dialog box update. The Staff ID column in the results does not contain any staff member IDs.

In FH Enterprise, if you tried to run the Dollar Loss Threshold Report with the steps below, an error message appeared.

Error 1526: Connectivity error. [Microsoft][ODBC SQL Server Driver][SQL Server]An expression of non-boolean type specified in a context where a condition is expected, near 'Lkp_inci'. at line 119 or procedure/method RPTRUN.DBSESSION.VIEWOPEN.

1. Choose Reports → Incident Reports.
2. In the Reports dialog box that appears, expand Incident Reports → NFIRS Incident Reports → Incident Statistical → Incident Statistical Detail.
3. Select Dollar Loss Threshold Report, and then click Run.
4. In the Output Report To dialog box that appears, select the output for the report as normal, and then click OK.
5. In the Query Parameters dialog box that appears, in the Incident Type row, in the Criteria column, click the cell and select In List of Values from the menu that appears.
6. In the Incident Type row, in the Value column, click the lookup button.
7. In the Lookup dialog box that appears, hold down the Ctrl key on the keyboard, select several different incident types, and then click OK.

8. In the Query Parameters dialog box, click Run Query.

   The error message appeared.

If you downloaded a checklist from FH to a barcode scanner, and then began an inventory session on the scanner with the steps below, the list of staff members that appeared on the scanner included staff members marked as hidden in FH.

1. On the barcode scanner, choose Start → Programs → FHScan.
2. In FHScan login dialog box that appears, using the keypad on the scanner, type your FH credentials, and then touch Login with the scanner's stylus or your finger.
3. On the next screen that appears, at the inventory check-in function prompt, touch Inventory.
4. On the next screen that appears, scan the barcode of the apparatus the inventory is being performed for, or manually enter the barcode number on the scanner keypad, and then either touch Look-Up or press Ent on the keypad.
5. On the next screen that appears, from Type, use the scanner’s stylus to select the checklist you want to use for this session, and then press Ent.
6. (If Odometer and/or Hours appear on the scanner) Enter the odometer reading, and/or hours meter reading.

7. Touch OK.

   A full list of staff members appears. This list includes even inactive staff members, that are marked as hidden in FH, and should not.

If you ran the Hydrant Management Report and sent the output to a PDF file with the steps below, in the Subtotal Flow Tests section, the Min row displays zeros (0) in all the columns.

1. Choose Reports → Hydrant Management Reports.
2. In the Reports dialog box that appears, expand Hydrant Management Reports → Hydrant Activity Reports.
3. Select Hydrant Flow Test By Hydrant, and then click Run.

4. In the Output Report To dialog box that appears, select the PDF, and then click OK.

   In the resulting PDF file, in the Subtotal Flow Tests section, the Min row displays zeros (0) in all the columns.

If you change the ability of a group of users to edit the passwords of non-administrator users with the steps below, the Change Password option is not active in the Tools menu as expected.

1. Log into FH as an administrator.
2. Choose Administration → Users and Security.
3. In the Users and Security dialog box that appears, click the User Groups tab.
4. Under Group Name, select a group, and then click Properties.

5. In the User Group Setup dialog box that appears, on the General tab, under Administrative Access, clear Full Administrative Access.

   All selected options under Administrative Access and General Privileges clear.

6. Under Administrative Access, select Change other non-admin passwords.

   In the confirmation dialog box that appears, click OK.

7. Click Save.
8. In the Users and Security dialog box, click Close.
9. Log out of FH.
10. Log back into FH as the user in the group you just edited.

11. Click the Tools menu.

    The Change Password option is not active in the Tools menu as expected.

In the inventory record, if you used the Unit field to indicate that the inventory item is located on a particular unit, then installed the NEMSIS code set with the steps below,the following error message appeared.

Your Nemsis configuration is not complete.

1. Open an inventory record as normal.
2. In the upper right corner of the dialog box, in Unit, type in or use the lookup button to select a unit.

3. Install the NEMSIS code set and configure it as normal.

   Information on installing and configuring for NEMSIS is available in NEMSIS Installation and Implementation Guide, available at http://www.firehousesoftware.com/webhelp/FH/Default.htm, under FH Installation, Update, Upsizing, and Administration Guides.

   In the inventory record, the Unit field is intended to specify the call sign for the unit. If you used this field to indicate that the inventory item is located on a particular unit, the error message appeared.

   The correct field to use for indicating that an inventory item is on a particular unit is Linked to Inventory ID.

If you are using the state-specific NEMSIS code set for Alaska, and had assigned the lookup code E10_01 Bites for a cause of injury value with the steps below, when you exported the NEMSIS data, FH exported the code as 1885 instead of 9510 (the correct code).

1. Begin a new EMS record as normal.
2. Click the Patients/Victims tab.
3. Click Add.
4. In the Patient/Victim Information dialog box that appears, click the Provider tab.
5. Under Provider Impression, for Mechanism of Injury/Nature of Illness, click the lookup button.
6. In the lookup dialog box, select E10_01 Bites, and then click OK.
7. Finish filling out and saving the patient/victim and EMS records as normal.

8. Export the NEMSIS data to a report for Alaska as normal.

   FH exported the code as 1885 instead of 9510 (the correct code).

If you changed an incident's type to one in the 800 range of lookup codes, and then ran the Incident Type Summary By District report with the steps below, the column totals were not accurate.

1. Open an incident record as normal.
2. In the NFIRS Incident Report dialog box that appears, on the Basic tab, under Incident Type, change the incident type to one of the incident types in the 800 range of lookup codes.
3. Save and close the record as normal.
4. Choose Reports → Incident Reports.
5. In the Reports dialog box that appears, expand Incident Reports → NFIRS Incident Reports → Incident Statistical → Incident Statistical Summary.
6. Select Incident Type Summary By District.

7. Run the report as normal, using no filters.

   In the resulting report, the Weather column displays all zeros (0), and one of the entries should be 1 to reflect the incident whose type you changed. The main total in the Total column is also off by one.