The information in this article applies to:
This article discusses methods of transferring Tabs3 Remote data to the main Tabs3 installation. KB Article R10443, "Tabs3 Remote File Name Specifications" contains a list of Tabs3 Remote data files that must be transferred to the main Tabs3 installation.
Additionally, a section discussing batch files is included along with a sample batch file that can be used to simplify the file transfer process.
When the data files are received by the location that has the main Tabs3 installation, it is recommended that when they are copied from the download directory into the main Tabs3 working directory, a copy is left in the download directory in case there are problems with the Merge Tabs3 Remote Data process.
E-mailing file attachments and transferring data over the Internet via File Transfer Protocol (FTP) are two common methods of transferring data quickly between two offices that are far apart. Unfortunately, sending multiple files at once using these methods increases the likelihood that the data may be corrupted in transit. Compressing the data using a compression utility such as PKZIP.EXE is a good way to ensure that your data is received intact and secure.
Transmitting compressed data via the Internet provides the following advantages over transmitting uncompressed data:
For more information regarding data compression, please see KB Article R10783, "Compressing Data Files."
If you have questions about using e-mail attachments or FTP to transfer your Tabs3 Remote data files, please consult your network administrator.
Some firms prefer to transfer the Tabs3 Remote data by storing the data on a floppy disk (provided the data files do not exceed the floppy disk capacity), an Iomega® Zip disk, or CD-ROM, etc. and then shipping or delivering the physical media to the location that has the main Tabs3 installation. Using a Zip disk or CD-ROM is especially popular when the data files to be transferred are extremely large. Using e-mail or FTP to transfer large files, even compressed, may take a long time and is subject to potential Internet interference, which might result in having to start the transfer over from the beginning. Using physical media such as a Zip disk or a CD-ROM may be faster than Internet transmission since transfer rates for Zip drives or CD-RW drives are significantly faster than the upload and download rates afforded by most Internet connections. This method also offers greater security and control over the data being sent as compared to Internet transmission, since it never leaves the control of the firm's employees. The downside of this method is that it may take time or expense to get the disk or CD-ROM to the main Tabs3 location.
Firms that have Tabs3 Remote installed on their local workstations and have the main Tabs3 installation on another machine on the same network can transfer the data files without need for Internet transmission or separate physical media. Typically, firms in this situation have one or more intermediate directories on the network file server, to which the Tabs3 Remote data files are copied. One of the users of the main Tabs3 system then copies the files from the intermediate directory to the Tabs3 working directory and imports the data into Tabs3. Once the import is complete, the files are deleted from the intermediate directory, and the process can be repeated for the next Tabs3 Remote workstation.
When running the Merge Tabs3 Remote Data program in Tabs3, it is possible to receive the following message:
Tabs3 and Remote data do not match.
This message can occur for two reasons:
A common reason for Tabs3 and Tabs3 remote to have different serial numbers is when the Tabs3 serial number has changed due to an upgrade or a firm name change, but Tabs3 Remote was not installed with the same serial number before the data was entered. Keep in mind that a different message will be seen if the remote data files are a different version than Tabs3.
For this situation, you can use the following procedure to resolve this message:
Note: This message can be avoided by merging the remote data from every computer that uses Tabs3 Remote before installing the new software (i.e., the different serial number) on the main Tabs3 computer or on the remote machines.
If the Tabs3 and Tabs3 Remote serial numbers match, determine whether the RMTFEEID.DAT or RMTCSTID.DAT file exists with the other RMT*.* files that are used to merge data. If one does not, perform the following steps:
When the reindex has completed, RMTFEEID.DAT will exist in the Tabs3 Remote directory. Copy this file to the main Tabs3 directory (with the other Tabs3 Remote data files) and merge the Tabs3 Remote data.
You may want to consider creating batch files to automate repetitive file transfer processes and make it easier for the Tabs3 Remote and Tabs3 operators. Using batch files will save time for the data entry operator and reduce the possibility of operator errors during the transfer process. Once the batch files have been created, you can add shortcuts/icons to the appropriate workstations for the required tasks.
Batch files can be created using either a text editor or word processor. However, if you use a word processor to create a batch file, you must save the file in an ASCII file format.
We have provided a sample batch file that can be used as a basis for creating your own batch file. If you need assistance with creating and/or implementing batch files, contact your local Tabs3 reseller or a consultant.
Note: The following batch file assumes that the intermediate media used to transfer files between Tabs3 Remote and Tabs3 is a floppy disk.
Remote data files created in Tabs3 Remote must be transferred and merged into the main Tabs3 computer periodically. The following is an example of a batch file that can be used to transfer the remote data files from the Tabs3 remote computer to a floppy disk. This floppy disk is then given to the Tabs3 operator.
In addition to transferring the files to a floppy disk, the batch file also transfers the files to a temporary directory and then deletes the remote files from the remote computer. Deleting the remote data files is required in order to prevent duplicate entries. Furthermore, the remote operator can continue data entry without waiting for the merge process to complete.
Note: The following batch file assumes that the Tabs3 Remote data is located on drive C in a directory named STI and that the floppy disk drive is drive A. This batch file also assumes that a subdirectory (folder) named
"TEMP" exists below the C:\STI directory. You can replace the appropriate paths with your system's paths as required. Consider naming this file RMT2DISK.BAT.
ECHO OFF
IF EXIST C:\STI\RMT*.* GOTO :TRANSFER
ECHO No remote data files to transfer.
GOTO :EXIT
:TRANSFER
ECHO Please insert a floppy disk in drive A:
PAUSE
ECHO ON
DEL A:RMT*.*
COPY C:\STI\RMT*.* A:
DEL C:\STI\TEMP\RMT*.*
COPY C:\STI\RMT*.* C:\STI\TEMP
DEL C:\STI\RMT*.*
:EXIT
The first part of the batch file verifies that there are remote data files on the remote workstation. If no files exist, the program does not execute. This prevents deletion of the remote files if the program is accidentally run twice.
The DEL A:RMT*.* line deletes any RMT*.* files on the floppy disk. This prevents possible duplication of any information. For example, let's say the same disk is used for each transfer and the last time it was used both fee and cost files were transferred. This time, only fee transactions are present. Transferring the fee files onto a floppy disk that has old fee and cost files creates a situation where the new fee files overwrite the old fee files but the old cost files are not overwritten. Therefore, the old cost files would be transferred to the Tabs3 computer and merged again thus creating duplicate cost entries.
The COPY C:\STI\RMT*.* A: line copies the remote data files to the floppy disk. This floppy disk will be given to the main Tabs3 operator to merge the information into Tabs3.
The DEL C:\STI\TEMP\RMT*.* line deletes any RMT*.* files that were placed in the TEMP directory from the last merge.
The COPY C:\STI\RMT*.* C:\STI\TEMP line copies the RMT*.* files to the TEMP directory. These files are copied to this temporary holding area in the event a problem arises when the Tabs3 operator attempts to merge the Tabs3 Remote data (i.e., floppy disk lost or damaged).
The DEL C:\STI\RMT*.* line deletes the RMT*.* files from the remote data directory. This allows the remote data entry operator to enter data in new remote data files. Otherwise, duplicate transactions will result the next time the data is merged.
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