|
|
|
|
The information in this article applies to:
This article discusses User IDs in Tabs3 and PracticeMaster software products, and the consequences and error messages involved with improperly resetting users.
System Configuration, included with all versions of Tabs3 and PracticeMaster software programs, is used to assign Tabs3 and PracticeMaster software users unique User IDs. Providing each user with a unique User ID is strongly recommended. Doing so makes it possible to determine who is using the software and what programs are being used at any given time.
It is important for each user to exit Tabs3 and PracticeMaster software properly by using one of the following methods:
This is important because User IDs are automatically logged out of the software when the program is closed properly. If a Tabs3 or PracticeMaster program is shut down improperly (e.g., by shutting down or rebooting the computer without first closing the application), the User ID will remain logged into the software. This may cause the message "Duplicate User IDs Were Found" to occur the next time the user attempts to log into the software. It may also interfere with the ability of other users to perform exclusive functions in the software.
User IDs that are assigned to the Manager Access Profile via the System Configuration program (i.e., User IDs with manager rights) have the ability to log User IDs out of the software by resetting them. Only User IDs that have exited the software improperly should be reset.
Some common reasons a user may be present in the Active User List while not actually logged into the software include:
IMPORTANT: Users that are actually logged into the Tabs3 and PracticeMaster software should NEVER be reset. If it becomes necessary to remove a User ID from the software, contact the user and ask them to log out. If the user is unavailable, go to the user's computer and close the program(s) yourself. Resetting users that are actually using a Tabs3 or PracticeMaster program can cause data loss, data corruption, and fatal errors in the data files.
In the event that a User ID is logged into the Tabs3 or PracticeMaster software and you are certain that nobody is physically logged into the program with that User ID, the User ID may be reset by using the following procedure:
Note: To view User IDs logged into all Tabs3 and PracticeMaster software, select the All Systems check box in the Active User List.
When a user is improperly reset (i.e., the user was actually using the software during a reset), that user receives the following message: "System activity information has been reset. You will have to exit the program." If this message occurs, one of the following situations may have occurred:
Clicking OK to clear this message automatically closes the Tabs3 or PracticeMaster software program. When a user has been improperly reset, it is important that the Data File Integrity Check program be run as soon as possible (as well as the Archive Data Integrity Check program if using Tabs3). Data corruption may have occurred as a result of the improper resetting, and a delay in running the integrity checks may result in extra work if it becomes necessary to restore from a backup.
If this message occurs, it is important to take measures to prevent it from occurring again. This article includes methods to help reduce the frequency of improper resets.
If multiple users have access to the Tabs3 and PracticeMaster software, even in a single user program, it may be useful to review the Reset Log to determine the User ID that was used to improperly reset another User ID. The Reset Log can be viewed by selecting View | Log Files | Reset Log.
A sample Reset Log is provided below.
System: T3 Date: 11-18-2009 Time: 14:53:52 User "ROBERT" Computer: \\Robert Reset User "JOHNT" in T3. System: T3 Date: 11-22-2009 Time: 09:02:43 User "MARK" Computer: \\Mark Reset User "ROBERT" in T3. System: PM Date: 12-06-2009 Time: 15:12:22 User "MARK" Computer: \\Mark Reset User "JOHNT" in PM. System: SC Date: 12-09-2009 Time: 10:13:02 User "MARK" Computer: \\Mark Reset User "ROBERT" in G5.
Each item in the log is defined in the table below.
|
Field |
Definition |
||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
System |
The System indicates which Tabs3 and PracticeMaster product was used by the user who did the resetting. Possible values include the following:
|
||||||||||||||
|
Date |
Date indicates the date on which the reset occurred. |
||||||||||||||
|
Time |
Time indicates the time of day the reset occurred, based on the system time of the computer from which the resetting was done. The improper reset line, which starts with two asterisks, indicates the time of day the task was actually reset on the workstation, based on the workstation time. (Note: This portion was added with the release of Version 14.2.) |
||||||||||||||
|
User |
User indicates the User ID that was used to perform the reset. |
||||||||||||||
| Computer | Computer specifies the workstation that was used to perform the reset. (Note: This portion was added with the release of Version 14.2.) | ||||||||||||||
|
Reset User |
Reset User specifies the User ID that was reset. |
||||||||||||||
|
In |
The software that was being used by the User ID that was reset. The
possible values are the same as those in the System field. |
In addition to the sample above, the Reset Log in Version 14.2 and later includes an additional line for every task users are accessing when improperly reset (i.e., reset while actively working in the software). These additional lines start with two asterisks.
A sample Reset Log with an improper reset indication is show in the following:
System: T3 Date: 10-25-2009 Time: 14:01:34 User "JULIE" Computer: \\Julie Reset User "JULIE" in T3. System: T3 Date: 10-25-2009 Time: 14:01:38 User "JULIE" Computer: \\Julie Reset User "RON" in PM. System: T3 Date: 10-25-2009 Time: 14:01:42 User "JULIE" Computer: \\Julie Reset User "RON" in PM. **System: PM Date: 10-25-2009 Time: 14:03:41 User "RON" was Reset while in Journal File. **System: PM Date: 10-25-2009 Time: 14:03:41 User "RON" was Reset while in Related Party File (Ctrl+Shift+P)
This sample shows that user Julie reset her own duplicate user while in Tabs3. However, she also reset Ron in PracticeMaster while he was accessing the Journal File and the Related Party File. If a user is in the software and is reset (a situation that should not occur), when that user ends the current task or attempts to start a new task, a message will be displayed indicating that system activity has been reset and the user must exit the program. When this message is displayed, a line is added to the Reset Log for every active task that user had open. This line starts with two asterisks (**).
The only time a user should be reset is when the user is not in the software. The Reset Log should not have lines that start with asterisks. If the Reset Log has lines that start with asterisks, this indicates incorrect use of the reset feature by one or more users, which can cause data loss, data corruption, and fatal errors. Regarding the sample above, we strongly recommend that the system administrator educate user "JULIE" regarding proper use of the reset function or restrict her rights to prevent future improper resetting.
Taking a proactive approach to system administration may help prevent the loss of time, money and resources that can result from data corruption. We recommend that your network or billing system administrator take the following preventative measures:
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-2010 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
