Log Off Users

 

Many firms use the Data File Integrity Check startup option in a batch file to ensure that the Data File Integrity Check is run on a regular basis. However, if other users remain logged in while the batch file is running, this can result in a Conflicting Activities window being displayed, thereby preventing the batch file from proceeding until all of the conflicting users log out.

The Log Off Users startup option allows Platinum firms to use the Request Log Off feature from the command line or a batch file to automatically log out any users whose current activities would conflict with a Data File Integrity Check prior to running the Data File Integrity Check. This can be helpful when running integrity checks as part of a batch process (e.g., before running an external backup). Users whose current activity does not conflict with an integrity check will remain logged in.

Note: All users currently in the software will be logged off immediately, closing their applications and discarding any unsaved work. Additionally, they will receive a notification with “Command Line Log Off” specified as the reason for the log off.

Note: This startup option will only log off users whose current activities would conflict with a Data File Integrity Check. If you need to force all users to exit the Tabs3 Software, the Log Off All Users startup option can be used instead.

An example of the Log Off Users startup option follows:

"C:\Tabs3\TBMAIN.EXE"  /LOG_OFF_USERS

Notes:

• The /LOG_OFF_USERS startup option cannot be combined with any startup options other than the USERID. It must be used as a separate command line when used in a batch file.
• If a USERID is specified, the user must have access rights to the Log Off Users feature. In addition, if the USERID requires a password, it must be manually entered when the software is launched.
• When used as part of a batch file, one of the following executables must be specified to ensure that the subsequent command in the batch file does not begin until the Log Off Users process is complete.
  • TBMAIN.EXE (Tabs3 Billing)
  • CMMAIN.EXE (PracticeMaster)
  • APMAIN.EXE (AP)
  • GLMAIN.EXE (GL)
  • TRMAIN.EXE (Trust)

See Knowledge Base Article R11034, “Automating Tabs3 Software Maintenance Tasks,” for more information.

Important Note: The Log Off Users startup option will not execute if an instance of the product with which it was launched with is already running on the workstation. For example, if a user is currently running Tabs3 Billing on their workstation, and Tabs3 Billing is launched using the Log Off Users startup option on the same workstation, the Log Off Users process will not be initiated. Therefore, we recommend that any batch files that use the Log Off Users startup option be launched from the server or a workstation where users do not normally log into the Tabs3 Software.

See also:	Adding a Startup Option
	Startup Options
	Startup Options: Log Off All Users
	Request Log Off
	Knowledge Base Article R11034 - Automating Tabs3 Software Maintenance Tasks