The information in this article applies to:
Note: As of Version 16, the name Client Server Version (CSV) has been replaced with Platinum. All references to Platinum or Platinum Version software in this article also apply to the Client Server Versions listed above unless specifically noted.
Various log files are maintained by different Tabs3 and PracticeMaster software products. These log files can be used as tools for troubleshooting errors and problems using Tabs3 and PracticeMaster software. This article contains a comprehensive list of the various log files and a brief description of the information contained in each file. Log files track errors encountered when running Tabs3 and PracticeMaster software as well as track the date and time when a particular function was performed. Log files can be accessed using any text editor such as Microsoft Notepad or WordPad. Most log files are located in the Tabs3 and PracticeMaster program directory; exceptions are noted. Log files that are specific to Version 12 are also noted.
Log files are created by the following programs:
STSUPPRT.DAT/IDX - The Support Log tracks various features performed in Tabs3 and PracticeMaster software. Each time one of the tracked features is performed, an entry is made in the Support Log. Refer to KB Article R11288, "Support Log Information (Ver. 15)" or KB Article R11054, "Support Log Information (Ver. 14 & 12.2)" for detailed information about this log file.
HOTSYNCLOG.HTM or HOTSYNC.LOG (Depending on HotSync® version) - This log file provides information about the last ten HotSync procedures and is created even if no errors are encountered. This log file contains errors encountered during a HotSync between Tabs3 and PracticeMaster Software (i.e., Tabs3 Palm Application and DTE InHand) and a Palm Handheld. It also contains errors encountered when HotSyncing other software with a Palm Handheld. This log file is created by the HotSync process and is located in the specific user's Palm Handheld directory (e.g., C:\Palm\Robert).
REBLDLDG.LOG - This log file includes the date and time when the Rebuild Client Ledger Detail program was run prior to Version 14. It also records the user which ran the rebuild, which clients it was ran for and how many detail records were created.
RESET.LOG - This log file contains information regarding the resetting of users within Tabs3 and PracticeMaster software. Provides a way to monitor which users are resetting other users, which users are being reset, and when the reset was performed. This file is not created until a reset has been performed. Refer to KB Article R10789, "Resetting Users" for detailed information about this log file.
STCTREE.LOG - This log file includes information regarding the Reindex Data Files program. Faircom (the provider of CTREE) generates this log.
STERROR.XML - This file includes all fatal or exception errors generated by a Tabs3 or PracticeMaster program Version 15 and later. When this file reaches 2.5 MB, it will delete all but the most recent .5 MB of entries. All entries to this file are written in ascending order, but are displayed in descending order, allowing the most recent error to appear at the top when viewing the error file. Each entry will contain the system date, time the error occurred, and User ID who encountered the error. The Error Number, Error Message, Additional Information, Traceback Path, and File Handler are all stored with each entry. The Sent tag determines if this entry has already been submitted or not through the Automatic Error Reporting feature. A value of Y indicates that it has been submitted, whereas N indicates it has not yet been submitted.
STERROR(x).XML - This file is created if an error submission detects a malformed STERROR.XML file. The Tabs3 and PracticeMaster software will rename the STERROR.XML file to STERROR0.XML silently upon detecting a malformed entry, and if STERROR0.XML already exists it will increase the number to the next available integer, (i.e., if STERROR2.XML exists in the directory, the software would rename the file to STERROR3.XML).
STERROR.XSL - This file contains the formatting information for the STERROR.XML file.
STERROR.LOG - This log file includes all fatal or exception errors generated by a Tabs3 or PracticeMaster program Version 14.3 and earlier. The last 10000 lines of information are maintained in this file. However, when printing, only the last 300 lines will print. The log file contains the system date and time the error occurred as well as the User ID that encountered the error. The Error Number, Error Message, Additional Information, Traceback Path, and File Handler are also included in the log file. This log file is maintained indefinitely.
STNWSET.LOG - This log file includes the network setting changes made using the Network Settings program. Refer to KB Article R11309, "Network Settings Technical Information" for detailed information about this log file.
STNWTEST.LOG - This log file includes the parameters used to run the Network Test, along with setup information and test results for each workstation participating in the Network Test. Refer to KB Article R11310, "Network Test Log Technical Information" for detailed information about this log file.
STQBERR.LOG - This log file includes all errors encountered during the QuickBooks Integration process. The log file reports records that could not be added to one system or the other for various reasons.
T3AFIC.LOG - This log file includes errors encountered while running the Archive Data Integrity Check program in Tabs3. The log file also tracks the date and the start and stop time of the last Archive Data Integrity Check. It is maintained until the next Archive Data Integrity Check is run. The file is created even if no errors are found.
T3CMERR.LOG - This log file includes messages and errors generated while running the "Merge Practice Mgmt Client Changes" program. This file shows all clients that were added or changed as well as any clients that were rejected during the merge process. Rejected clients must be re-entered using the Client data entry program in Tabs3.
T3CMSYNC.LOG - This log file stores all changes that were made and records that were added when running the synchronization program in Tabs3. It is maintained until the next time the sync is run and is created even if no changes were made.
T3DFIC.LOG - This log file includes errors encountered while running the Data File Integrity Check program in Tabs3. The log file also tracks the date and the start and stop time of the last Data File Integrity Check. It is maintained until the next Data File Integrity Check is run. The file is created even if no errors are found.
T3PALM.LOG - This log file is created when HotSyncing with the Tabs3 Palm Application and includes any errors that were encountered during the HotSync process.
T3PILOT.LOG - This log file contains errors that may have occurred during the merge of data from a Palm Handheld into Tabs3 using the DTE InHand software. Examples include "invalid tcode or timekeeper" errors. This file is overwritten each time a HotSync is performed. This log file can be found in the Palm Handheld directory (e.g., C:\Palm).
T3REORG.LOG - This log file includes errors encountered while running the Reindex Data Files program in Tabs3. The log file also tracks the User ID, date, start and stop time of the last Reindex Data Files. It is maintained until the next time Reindex Data Files is run. The file is created even if no errors are found.
R3DFIC.LOG - This log file includes errors encountered while running the Data File Integrity Check program in Tabs3 Remote. The log file also tracks the date and the start and stop time of the last Data File Integrity Check. It is maintained until the next Data File Integrity Check is run. The file is created even if no errors are found.
R3REORG.LOG - This log file includes errors generated when running the Reindex Data Files program in Tabs3 Remote. The log file also tracks the User ID, date, start and stop time of the last Reindex Data Files. It is maintained until the next time Reindex Data Files is run. The file is created even if no errors are found.
RESET.LOG - This log file contains information regarding the resetting of users within Tabs3 and PracticeMaster software. Provides a way to monitor which users are resetting other users, which users are being reset, and when the reset was performed. This file is not created until a reset has been performed. Refer to KB Article R10789, "Resetting Users" for detailed information about this log file.
STCTREE.LOG - This log file includes information regarding the Reindex Data Files program. Faircom (the provider of CTREE) generates this log.
STERROR.XML - This file includes all fatal or exception errors generated by a Tabs3 or PracticeMaster program Version 15 and later. When this file reaches 2.5 MB, it will delete all but the most recent .5 MB of entries. All entries to this file are written in ascending order, but are displayed in descending order, allowing the most recent error to appear at the top when viewing the error file. Each entry will contain the system date, time the error occurred, and User ID who encountered the error. The Error Number, Error Message, Additional Information, Traceback Path, and File Handler are all stored with each entry. The Sent tag determines if this entry has already been submitted or not through the Automatic Error Reporting feature. A value of Y indicates that it has been submitted, whereas N indicates it has not yet been submitted.
STERROR(x).XML - This file is created if an error submission detects a malformed STERROR.XML file. The Tabs3 and PracticeMaster software will rename the STERROR.XML file to STERROR0.XML silently upon detecting a malformed entry, and if STERROR0.XML already exists it will increase the number to the next available integer, (i.e., if STERROR2.XML exists in the directory, the software would rename the file to STERROR3.XML).
STERROR.XSL - This file contains the formatting information for the STERROR.XML file.
STERROR.LOG - This log file includes all fatal or exception errors generated by a Tabs3 or PracticeMaster program. The last 3000 lines of information are maintained in this file. However, when printing, only the last 300 lines will print. The log file contains the system date and time the error occurred as well as the User ID that encountered the error. The Error Number, Error Message, Additional Information, Traceback Path, and File Handler are also included in the log file. This log file is maintained indefinitely.
A3DFIC.LOG - This log file includes errors encountered while running the Data File Integrity Check program in Accounts Payable. The log file also tracks the date and the start and stop time of the last Data File Integrity Check. It is maintained until the next Data File Integrity Check is run. The file is created even if no errors are found.
A3REORG.LOG - This log file includes errors encountered while running the Reindex Data Files program in APS. The log file also tracks the User ID, date, start and stop time of the last Reindex Data Files. It is maintained until the next time Reindex Data Files is run. The file is created even if no errors are found.
G5DFIC.LOG - This log file includes errors encountered while running the Data File Integrity Check program in General Ledger. The log file also tracks the date and the start and stop time of the last Data File Integrity Check. It is maintained until the next Data File Integrity Check is run. The file is created even if no errors are found.
G5DFIC76.LOG - This log file is created if an error 76 is encountered when running the Data File Integrity Check program in General Ledger. The log file shows the date, the time and the GLS client for which the Integrity Check was run. The purpose of the log file is to provide an audit trail of the old and new (adjusted) balances for each month in which the balance of the type R (retained earnings) account did not match the Balance Sheet. If the log file already exists when an error 76 is encountered, GLS appends to the file. Additional information regarding the DFIC error 76, including an example of the G5DFIC76.LOG file, can be found in KB Article R10980, "DFIC Error 76 - Retained Earnings Mismatch".
G5REORG.LOG - This log file includes errors encountered while running the Reindex Data Files program in GLS. The log file also tracks the User ID, date, start and stop time of the last Reindex Data Files. It is maintained until the next time Reindex Data Files is run. The file is created even if no errors are found.
RESET.LOG - This log file contains information regarding the resetting of users within Tabs3 and PracticeMaster software. Provides a way to monitor which users are resetting other users, which users are being reset, and when the reset was performed. This file is not created until a reset has been performed. Refer to KB Article R10789, "Resetting Users" for detailed information about this log file.
STCTREE.LOG - This log file includes information regarding the Reindex Data Files program. Faircom (the provider of CTREE) generates this log.
STERROR.XML - This file includes all fatal or exception errors generated by a Tabs3 or PracticeMaster program Version 15 and later. When this file reaches 2.5 MB, it will delete all but the most recent .5 MB of entries. All entries to this file are written in ascending order, but are displayed in descending order, allowing the most recent error to appear at the top when viewing the error file. Each entry will contain the system date, time the error occurred, and User ID who encountered the error. The Error Number, Error Message, Additional Information, Traceback Path, and File Handler are all stored with each entry. The Sent tag determines if this entry has already been submitted or not through the Automatic Error Reporting feature. A value of Y indicates that it has been submitted, whereas N indicates it has not yet been submitted.
STERROR(x).XML - This file is created if an error submission detects a malformed STERROR.XML file. The Tabs3 and PracticeMaster software will rename the STERROR.XML file to STERROR0.XML silently upon detecting a malformed entry, and if STERROR0.XML already exists it will increase the number to the next available integer, (i.e., if STERROR2.XML exists in the directory, the software would rename the file to STERROR3.XML).
STERROR.XSL - This file contains the formatting information for the STERROR.XML file.
STERROR.LOG - This log file includes all fatal or exception errors generated by a Tabs3 or PracticeMaster program. The last 3000 lines of information are maintained in this file. However, when printing, only the last 300 lines will print. The log file contains the system date and time the error occurred as well as the User ID that encountered the error. The Error Number, Error Message, Additional Information, Traceback Path, and File Handler are also included in the log file. This log file is maintained indefinitely.
STNWSET.LOG - This log file includes the network setting changes made using the Network Settings program. Refer to KB Article R11309, "Network Settings Technical Information" for detailed information about this log file.
STNWTEST.LOG - This log file includes the parameters used to run the Network Test, along with setup information and test results for each workstation participating in the Network Test. Refer to KB Article R11310, "Network Test Log Technical Information" for detailed information about this log file.
T4DFIC.LOG - This log file includes errors encountered while running the Data File Integrity Check program in Trust Accounting. The log file also tracks the date and the start and stop time of the last Data File Integrity Check. It is maintained until the next Data File Integrity Check is run. The file is created even if no errors are found.
T4REORG.LOG - This log file includes errors encountered while running the Reindex Data Files program in TAS. The log file also tracks the User ID, date, start and stop time of the last Reindex Data Files. It is maintained until the next time Reindex Data Files is run. The file is created even if no errors are found.
CMARCCMP.LOG - This log file contains information regarding the compression of E-mail Attachment files. This file includes the user performing the compression, the time and date the compression began, the file names before the compression, the file names after compression, and the time and date the compression completed. The file will only be created if the E-mail Attachments files are reindexed with the Compact checkbox selected and will be overwritten the next time the compression is performed.
CMBCERR.LOG - This log file contains any errors encountered during the Briefcase check in process. This file includes the location of the Briefcase data and the location of the host data. For each error generated, the Area of Practice, File, Record Key, Field, Field Type, Error and Briefcase Field Value are shown.
CMBRIEF.LOG - This log file contains information regarding all Briefcase check ins, check outs and clearing of check outs. This file includes the function performed, the date and time the function was performed, which user performed the function, and the directory for the data. When Briefcase data is checked in, this log file also indicates whether the Process Deletions check box was selected. The CMBRIEF.LOG file is stored in the host PracticeMaster program directory. The maximum size of this file is 300 lines. Once the file reaches this limit, any data written to the file will begin replacing the oldest data to make room for the new data.
CMDFIC.LOG - This log file includes errors encountered while running the Data File Integrity Check program in PracticeMaster. The log file also tracks the date and the start and stop time of the last Data File Integrity Check. It is maintained until the next Data File Integrity Check is run. The file is created even if no errors are found.
CMIMPORT.LOG - This log file includes errors that were encountered during the import. The log file contains the path and filename of the file being imported and the file that it is being imported into. It is maintained until the next import is run. The file is created even if no errors are found.
CMOL_????.LOG (Version 15, 14, and 12) - This log file stores the information about the last time the Outlook Synchronization program was run. It lists any records added, changed or deleted in PracticeMaster and/or Outlook, and it includes the start date and time, User ID, and completed date and time of the synchronization program. This log file is maintained until the next time the program is run and is created even if no changes were made. The question marks represent the User ID that is performing the Outlook Synchronization.
CMOLLOG.DAT/IDX (Version 16) - This log file stores all changes made during the Outlook synchronization process. It lists any records added, deleted, and changed, as well as any errors that were encountered, for all users who are set up to integrate with Outlook.
CMPALM.LOG - This log file is created when HotSyncing with the PracticeMaster Palm Application. It includes any errors that were encountered during the HotSync process.
CMREORG.LOG - This log file includes errors encountered while running the Reindex Data Files program in PracticeMaster. The log file also tracks the User ID, date, start and stop time of the last time Reindex Data Files was run. It is maintained until the next time Reindex Data Files is run. The file is created even if no errors are found.
CMT3SYNC.LOG - This log file stores all changes that were made and records that were added when running the synchronization program in PracticeMaster. It is maintained until the next time the sync is run and is created even if no changes were made.
CMUPD???.LOG - This log file is created when PracticeMaster files are updated and includes any changes that were made to PracticeMaster files or fields. It also contains the date and time that the update was performed, when it completed and the User ID of the person that ran the update. The question marks represent the number of updates.
CONFLICT.LOG - This log file stores information about the last time the Conflict of Interest Configuration program was run. It includes the date and time it was run as well as information about the number of files that were checked and the elapsed time. It is maintained until the next time Conflict of Interest Configuration program is run.
HOTSYNCLOG.HTM or HOTSYNC.LOG (Depending on HotSync® version) - This log file provides information about the last ten HotSync procedures and is created even if no errors are encountered. This log file contains errors encountered during a HotSync between Tabs3 or PracticeMaster Software (i.e., Palm Conduits and PracticeMaster Palm Application) and a Palm Handheld. It also contains errors encountered when HotSyncing other software with a Palm Handheld. This log file is created by the HotSync process and is located in the specific user's Palm Handheld directory (e.g., C:\Palm\Robert).
RESET.LOG - This log file contains information regarding the resetting of users within Tabs3 and PracticeMaster software. Provides a way to monitor which users are resetting other users, which users are being reset, and when the reset was performed. This file is not created until a reset has been performed. Refer to KB Article R10789, "Resetting Users" for detailed information about this log file.
SEARCH.LOG - This log file maintains entries of when the Search index files are rebuilt. Each entry shows the time the rebuild was started, total memory and available memory, and each phase that the rebuild went through.
STCTREE.LOG - This log file includes information regarding the Reindex Data Files program. Faircom (the provider of CTREE) generates this log.
STERROR.XML - This file includes all fatal or exception errors generated by a Tabs3 or PracticeMaster program Version 15 and later. When this file reaches 2.5 MB, it will delete all but the most recent .5 MB of entries. All entries to this file are written in ascending order, but are displayed in descending order, allowing the most recent error to appear at the top when viewing the error file. Each entry will contain the system date, time the error occurred, and User ID who encountered the error. The Error Number, Error Message, Additional Information, Traceback Path, and File Handler are all stored with each entry. The Sent tag determines if this entry has already been submitted or not through the Automatic Error Reporting feature. A value of Y indicates that it has been submitted, whereas N indicates it has not yet been submitted.
STERROR(x).XML - This file is created if an error submission detects a malformed STERROR.XML file. The Tabs3 and PracticeMaster software will rename the STERROR.XML file to STERROR0.XML silently upon detecting a malformed entry, and if STERROR0.XML already exists it will increase the number to the next available integer, (i.e., if STERROR2.XML exists in the directory, the software would rename the file to STERROR3.XML).
STERROR.XSL - This file contains the formatting information for the STERROR.XML file.
STERROR.LOG - This log file includes all fatal or exception errors generated by a Tabs3 or PracticeMaster program. The last 3000 lines of information are maintained in this file. However, when printing, only the last 300 lines will print. The log file contains the system date and time the error occurred as well as the User ID that encountered the error. The Error Number, Error Message, Additional Information, Traceback Path, and File Handler are also included in the log file. This log file is maintained indefinitely.
STNWSET.LOG - This log file includes the network setting changes made using the Network Settings program. Refer to KB Article R11309, "Network Settings Technical Information" for detailed information about this log file.
STNWTEST.LOG - This log file includes the parameters used to run the Network Test, along with setup information and test results for each workstation participating in the Network Test. Refer to KB Article R11310, "Network Test Log Technical Information" for detailed information about this log file.
STQBERR.LOG - This log file includes all errors encountered in the process of QuickBooks Integration. The log file reports records that could not be added to one system or the other for various reasons.
RESET.LOG - This log file includes information when a user is reset using the Active User List program. The log file contains which user performed the reset, which user was reset, which system was reset, and the date and time that the system was reset. The release of Version 10.7 in December 2002 added the system in which the reset was performed.
SCREORG.LOG (Version 10.5 and later) - This log file includes errors encountered when running the Reindex Data Files program in System Configuration. The log file also tracks the User ID, date, start and stop time of the last time Reindex Data Files was run. It is maintained until the next time Reindex Data Files is run. The file is created even if no errors are found.
STERROR.XML - This file includes all fatal or exception errors generated by a Tabs3 or PracticeMaster program Version 15 and later. When this file reaches 2.5 MB, it will delete all but the most recent .5 MB of entries. All entries to this file are written in ascending order, but are displayed in descending order, allowing the most recent error to appear at the top when viewing the error file. Each entry will contain the system date, time the error occurred, and User ID who encountered the error. The Error Number, Error Message, Additional Information, Traceback Path, and File Handler are all stored with each entry. The Sent tag determines if this entry has already been submitted or not through the Automatic Error Reporting feature. A value of Y indicates that it has been submitted, whereas N indicates it has not yet been submitted.
STERROR(x).XML - This file is created if an error submission detects a malformed STERROR.XML file. The Tabs3 and PracticeMaster software will rename the STERROR.XML file to STERROR0.XML silently upon detecting a malformed entry, and if STERROR0.XML already exists it will increase the number to the next available integer, (i.e., if STERROR2.XML exists in the directory, the software would rename the file to STERROR3.XML).
STERROR.XSL - This file contains the formatting information for the STERROR.XML file.
STERROR.LOG - This log file includes all fatal or exception errors generated by a Tabs3 or PracticeMaster program. The last 3000 lines of information are maintained in this file. However, when printing, only the last 300 lines will print. The log file contains the system date and time the error occurred as well as the User ID that encountered the error. The Error Number, Error Message, Additional Information, Traceback Path, and File Handler are also included in the log file. This log file is maintained indefinitely.
STNWSET.LOG - This log file includes the network setting changes made using the Network Settings program. Refer to KB Article R11309, "Network Settings Technical Information" for detailed information about this log file.
STNWTEST.LOG - This log file includes the parameters used to run the Network Test, along with setup information and test results for each workstation participating in the Network Test. Refer to KB Article R11310, "Network Test Log Technical Information" for detailed information about this log file.
BACKUP.LOG - This file maintains a list of all HotBackups currently located in the Archive, Recent, and Failed subfolders. It will be found in the HotBackup root folder.
HB.LOG - This file maintains a detailed list of the specific actions that took place in order to create the HotBackup. The date and time of each action is also recorded in this file. An HB.LOG file is stored with each HotBackup, and is located in the folder for that HotBackup.
HBRESTORE.LOG - This file records what is done when a HotBackup is restored. If restoring a HotBackup to a new directory and making that location the current working directory, this file will provide the Data ID needed to complete the process. It will also log what files were copied successfully, and indicate any possible problems with the HotBackup Restore function.
HBQ.LOG - This file records all actions done by the HBQ.EXE program, and can be useful in troubleshooting Platinum Version installations.
TBDEVICE.LOG - This log file stores the last time the Conversion program was run. It lists any errors encountered during the conversion process and includes the date and time the conversion started and finished. It is maintained until the next time the Conversion program is run.
TSCONV.LOG - This log file includes messages and errors generated during the conversion process.
WCNVASCV.LOG - This log file includes errors encountered when running the WCNVASCV.EXE program and is recreated each time the program is run. If no errors were encountered, the file will be a 0 byte file.
STCONV16.LOG - This log file includes any errors encountered during the conversion as well as the status of whether each program will be converted or has already been converted to Version 16. This file will be created even if no errors are encountered (see KB Article R11357, "STCONV16.LOG Information" and KB Article R11356, "Messages During the Version 15 to Version 16 Conversion").
STCONV15.LOG - This log file includes any errors encountered during the conversion as well as the status of whether each program will be converted or has already been converted to Version 15. This file will be created even if no errors are encountered (see KB Article R11235, "STCONV15.LOG Information" and KB Article R11234, "Messages During the Version 14 to Version 15 Conversion").
STCONV14.LOG - This log file includes any errors encountered during the conversion as well as the status of whether each program will be converted or has already been converted to Version 14. This file will be created even if no errors are encountered (see KB Article R11086, "STCONV14.LOG Information" and KB Article R11085, "Messages During the Version 12 to Version 14 Conversion").
PMCONV14.LOG - This log file includes any file structure changes made to PracticeMaster during the conversion.
STCONV12.LOG - This log file includes any errors encountered during the conversion as well as the status of whether each program will be converted or has already been converted to Version 12. This file will be created even if no errors are encountered (see KB Article R10999, "STCONV12.LOG Information" and KB Article R11016, "Error Messages During the Version 11 to Version 12 Conversion").
PMCONV12.LOG - This log file includes any file structure changes made to PracticeMaster during the conversion.
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