December 15, 2005 | Mark Paradies

Tech Support Thursday: Creating and Sharing Equifactor Tables

Hello everybody, I’m back with another Tech Support Thursday.

Today I’m going to cover Equifactor tables, how to create and share them amongst users.

Basic Creation and Sharing of Equifactor Tables

If you use the Workgroup or Enterprise version of TapRooT System Software (read about the differences right here), whenever you create an Equifactor table, you are then sharing it automatically amongst your group of investigators and/or users.

However, for those without Workgroup or Enterprise editions, things get a little trickier. Let’s take a look:

Sharing Tables With A Single-User Version

There are two ways to share Equifactor tables in the System Software if you have a Single User version:

#1 – Copy and Restore the entire database on another machine

This isn’t the best option, not by a longshot. Why? Because this procedure will erase all data from the destination machine! This is fine if the destination machine has never had TapRooT System Software on it, but not so great for those that have existing incidents.

Best Practice: Create a new install. Create a “dummy” incident and create the new Equifactor troubleshooting tables in that incident. When you’re done, make sure you save the Incident (which will save the Equifactor tables as well), then delete the dummy incident. Afterwards, use the Database Backup and Restore procedures (read about them) so when you install a new copy of the System Software, before you do anything else restore that blank database with the new tables and they will be available on that machine from then on.

#2 – Use the Export/Import Feature To Copy Tables

If you use Version 4.0.5 or better of the TapRooT System Software, you have a feature on the Incident Manager called Import and Export. These are two functions which will allow you to remove isolated incidents from a database and insert them into another without destroying any data on the destination machine.

Best Practice: Here are the steps for creating tables that will export to other machines:

– Create a dummy incident in your database

– Create an Equifactor analysis inside it

– Check EVERY node that you want to transfer.

– SAVE and close the Incident.

– EXPORT the incident into a file.

Now, when you import that file into anyone else’s database (with the exact same version of course), your custom table will import with it. And the Equifactor tables will remain in the database even if you delete that dummy incident.

I hope this helped. Any questions, feel free to comment or use the Contact Us feature at the top of the page.

See you next week!

Categories
Software - Technically Speaking
Show Comments

Leave a Reply

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

Follow us on Facebook
Follow us on Twitter
Check out our videos
Join us on LinkedIn