August 28, 2008 |

Tech Support Thursday: New Dictionary Update Issue

Hello everybody, and welcome to another Tech Support Thursday. This week we’re going to talk about the latest TapRooT® System Software Dictionary Update that you may have installed over the past few months.

The update was to bring the Version 4 software and its associated content in-line with the new TapRooT® Dictionary that was released with the latest TapRooT® Book. And while it was updated with the latest wordings and definitions, its formatting turned out to have a few issues. They have to deal with Root Cause Tree® analysis comments and the dictionary formatting. Two things:

  • Bullet points (like the ones I’m using here) should never, ever be copied and pasted into Root Cause Tree® Analysis comments. If you do so, and you save the Causal Factor Root Cause Analysis, you will not be able to successfully import this incident into another installation until that Causal Factor is deleted and the analysis completed again. The bullet point character corrupts the database entry for that Causal Factor. Not rendering it useless on the originating machine, as you can still edit, look, and modify the Causal Factor properties and Root Cause Analysis, but any exported .TS4 files will not import into any other install and you will see a “Run-Time 91” error pop-up when trying to import it.
  • Quotes (” “) that are copied and pasted from the latest Root Cause Dictionary update will also cause this export/import issue. This is due to the character set used in the Dictionary Update.

Note that we’ve disabled any further downloads of the Dictionary Update while progress continues on the fixed version. The good news is, in the next few days you should see an update where you can find the latest version of the TapRooT® Dictionary that won’t corrupt your Root Cause Tree® analysis in the slightest. We’re working hard to get this update to you as soon as possible, as this problem just came to our attention recently.

Thanks for using TapRooT® and keep checking back for that update!

Show Comments

Leave a Reply

Your email address will not be published. Required fields are marked *