The information in this article applies to:
When a user leaves the firm, it may seem as though deleting the user is the best way to handle the situation. However, deleting a user can potentially cause Data File Integrity Check errors in Tabs3 and PracticeMaster. This article discusses alternatives to deleting a user. It also provides options for preventing errors as well as correcting errors that may result from deleting the user.
If you delete a User ID that has records associated with it, the next time a Data File Integrity Check (DFIC) is run in Tabs3 or PracticeMaster, an error code 145 (User ID Not Defined) will be generated for every record associated with the deleted User ID. The Data File Integrity Check determines whether a User ID is valid by comparing it to the User IDs currently defined in System Configuration. Therefore, deleting a User ID has the potential of generating thousands of error 145s, depending on the number of records that are associated with the User ID.
The following Tabs3 files include User ID fields that represent the user that created the record:
In Tabs3, these fields are assigned by the software. These fields can only be edited by a Manager. You can use the Reassign User ID program in System Configuration to globally reassign the User ID to a different User ID.
The following PracticeMaster files include User ID fields:
In PracticeMaster, the Fee and Cost files are identical to those in Tabs3, and therefore the User ID can only be edited by a Manager. You can use the Reassign User ID program in System Configuration to globally reassign the User ID to a different User ID. In the Calendar file, each record contains two User ID fields: the User ID field that is assigned by the software to represent the user that created the record, and the User/Group field assigned to the record. The User ID field in the Calendar file can only be edited by a Manager. You can use the Reassign User ID program in System Configuration to globally reassign the User ID to a different User ID.
The User/Group field in the Calendar file shares traits with the User ID field in the Journal file and the Responsible and Performed By fields in the Document Management file. These fields can be replaced using the Find and Replace feature in PracticeMaster.
If your firm has created or modified other files, these files may include User ID fields. If the field is Virtual, it cannot be replaced using the Find and Replace feature. Due to the History Tracking feature, all PracticeMaster records are tracked according to their creator. Therefore, regardless of the use of Find and Replace, you should still reassign a User ID before deleting it from System Configuration. If this is not done, DFIC error 145s may occur.
Note: If the User ID has already been deleted, you can re-create it in System Configuration. You do not need to know the user's original name or password to do this, only the exact User ID. Recreating the User ID will eliminate the DFIC error 145s.
System Configuration includes the ability to reassign existing Tabs3 and PracticeMaster records to a different User ID. This can be useful when someone leaves the firm. Before deleting the User ID of the person who left, you can use the Reassign User ID program (Utilities | Reassign User ID) to assign all existing records to a different User ID. For example, you might create a User ID called "PREVIOUS" that is used to track all records for people who have left the firm. When someone leaves, you could use the Reassign User ID program to change all records for that person's User ID to the PREVIOUS User ID. Then, you could delete the person's original User ID. Doing this prevents errors from arising as a result of deleting a User ID that was in use in one or more records.
Note: The Reassign User ID program is an all-inclusive procedure (i.e., when selecting to reassign records from one User ID to another, all records will be assigned to the other user).
System Configuration also offers the ability to mark a User ID as inactive. This is accomplished by selecting the Inactive check box in User Configuration (File | Open | Users). This is beneficial because the User ID is not deleted, and therefore no errors occur as a result of using this method. This method has the added benefit of preventing inactive User IDs from appearing in User ID Lookup windows. If these lookup windows are your main concern with regard to former employees' User IDs, marking the User ID inactive is a simple, effective solution.
Additionally, if you use the PracticeMaster software, you will want to remove the inactive users from any groups they are associated with in System Configuration (File | Open | Group). If you do not remove an inactive User ID from all associated groups, then any calendar records created in PracticeMaster for these groups will continue to include the inactive User ID, and thus new calendar entries will be created for the inactive User ID.
PracticeMaster Note: In order to prevent a User ID from being used to log in to PracticeMaster software, you must also clear the Logon User check box in User Configuration (File | Open | Users).
The PracticeMaster software offers the ability to find and replace some User ID fields with other User IDs. Whether you want to reassign and delete a former User ID or mark the User ID as inactive, it may be beneficial to replace the User ID in some PracticeMaster records with other User IDs. The Find and Replace feature in PracticeMaster can help you to do this. In some cases, it may be necessary to reassign future calendar records to another use, but maintain older records as historical information that must remain linked to the former user. Although you cannot replace the field that indicates who created the calendar record, you can replace contents of the User/Group field to reflect who will be taking over certain calendar records.
To replace a User ID in the Calendar file:
Although this removes the former User ID from current calendar records, you will still need to remove the User ID from any groups assigned in System Configuration. If this is not done and the user is marked as inactive (rather than reassigned and deleted), the user may continue to appear in future calendar records.
Steps similar to those above can be used to replace the User ID in the Responsible and Performed By fields in the Document Management file and the User ID field in the Journal file. If your firm has created or modified any other files, these files may include User ID fields. If the User ID field is Virtual, it cannot be replaced using the Find and Replace feature.
Note: Due to the History Tracking feature, all PracticeMaster records are tracked according to their creator. Therefore, regardless of the use of Find and Replace, you should still reassign a User ID before deleting it from System Configuration. If this is not done, DFIC error 145s may occur.
There are two recommended procedures:
The decision to use Option 1 versus Option 2 is determined by how much information you want to retain as belonging to the former user. If you want certain information to be retained as belonging to this particular former user, then Option 1 is the recommended option. If you want the user's records to become part of a single "Former User" entity, then Option 2 is the recommended option.
System Configuration offers the ability to mark a User ID as inactive. This is accomplished by selecting the Inactive check box in User Configuration. Additionally, if you use PracticeMaster, you will want to remove the inactive users from any groups they are associated with in System Configuration.
To mark a User ID as Inactive and prevent users from logging in with the User ID:
To remove a User ID from System Configuration groups:
System Configuration includes the ability to reassign existing Tabs3 and PracticeMaster records to a different User ID. Before reassigning a User ID, create a User ID that can be used to store the information of former users. Also, if you are a PracticeMaster user, you have the option of reassigning certain records to other users via the Find and Replace feature before reassigning the remaining records to a single User ID.
To create a User ID for former users:
To reassign user records to the collective User ID:
To delete a User ID:
THE INFORMATION PROVIDED IN THE SOFTWARE TECHNOLOGY, INC. KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SOFTWARE TECHNOLOGY, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.
© 1999-2012 Software Technology, Inc. All rights
reserved. Terms of Use
The maker of Tabs3 and PracticeMaster
Tabs3, PracticeMaster, and the “pinwheel” symbol (
) are registered trademarks of Software Technology, Inc.
e-Mail Suggestions for the Knowledge Base to: kb@Tabs3.com
Technical Support via e-mail is not available.
Knowledge Base: http://support.Tabs3.com
Web Site: http://www.Tabs3.com