1. Insert the TBDevice interface program disk into your floppy disk drive.
2. Click the Start button, and then click Run...
3. Type A:SETUP or B:SETUP (depending on the floppy drive used), and then click OK.
4. Follow the on-screen instructions to run the SETUP program.

Note: The TBDevice program (TBDEVICE.EXE) must be installed in the same directory where the Tabs3 program resides.

1. From the Software Technology folder, double-click the TBDevice icon to start the TBDevice program.
2. If the Logon dialog box is displayed, enter your User ID and Password and click OK.
3. From the File menu, select the Configure option.
4. The Configuration window will be displayed. Click the drop-down arrow next to the Device field and select ASCII Variable.
5. In the File field, type the name of the file containing the date from the collection device (i.e., TABS3.CV).
6. Select the Default check box if you want to make the ASCII Variable device the default in the Conversion program.
7. Click the More Config button.
8. In the Descriptions section, select the Upper Case Text if you want to use all upper case letters in the Tabs3 description.
9. Click OK.
10. Click the Save button.
11. Close the Configuration window.

1. Copy the file containing the data from the collection device (i.e., TABS3.CV) to the Tabs3 directory.
2. If the TBDevice program is already started, skip to step 4. From the Software Technology folder, double-click the TBDevice icon to start the TBDevice program.
3. If the Logon dialog box is displayed, enter your User ID and Password and click OK.
4. From the File menu, select the Convert option.
5. The Conversion window will be displayed. If the ASCII Variable device is not displayed in the Device field, click the drop-down arrow next to the Device field to select the ASCII Variable format.
6. Click the Convert button. The program will look for the file name TABS3.CV. If the file is found to contain data, the program will read transactions from the file and increment the Processed count for every transaction that is read. All transactions that are successfully converted will increment the Added count and will be written to the Tabs3 Remote data files (RMT*.*).

   Note: A TBDEVICE.LOG file is created and will contain any records that were not converted. If no errors were encountered during the conversion, then the TBDEVICE.LOG file will be a zero byte file.

   Note: If you are using a full user system, the ASCII Variable data file will automatically be deleted when the conversion is complete to avoid double posting of the data. However, when using a trial system, the data file is not deleted.

7. When the process is complete, the data files will have been created allowing you to merge the information into Tabs3 using the Merge Tabs3 Remote Data program. To merge the files, start Tabs3. From the Integration Task Folder, select Merge Tabs3 Remote Data. This program will merge the remote data files created by the TBDevice program (RMT*.*) with your main Tabs3 data files. The Tabs3 Help includes complete details regarding the Merge Tabs3 Remote Data program.

• Each field is delimited by a comma. The quotation marks at the beginning and end of each field are optional with the exception of the Description field. The Description field should begin and end with quotes (i.e., "text") so that commas in the Description field are not mistaken for a field delimiter. Also, embedded quotes in the Description text should be single quotes so they are not mistaken for boundary quotes (i.e. "this is a sample of ‘quoted’ text, with a comma within the text").
• The Client ID can be up to 12 characters in length. It must precisely match Client IDs that are entered into Tabs3.
• Fields 7 and 8 are ignored for payment transactions.
• If the Tabs3 client is not a Task Based Billing Client, the transaction code is converted and the Phase/Task Code and Activity Code fields are ignored. If the Tabs3 client is a Task Based Billing Client, the transaction code field is ignored (except for the "$" necessary to denote cost and payment transactions) and the Phase/Task Code and Activity Code fields are converted instead.
• If the Rate field is zero, then Tabs3 will supply the default rate assigned in the Tabs3 client record when the transaction is merged into Tabs3.
• If both Rate and Amount fields are zero, then Tabs3 will supply a default Rate and calculate the Amount automatically when the transaction is merged into Tabs3.
• When the data is merged into Tabs3, the Client ID, Timekeeper, and Transaction Code fields are verified as being valid. If the Tabs3 client is a Task Based Billing Client, the Phase/Task Code and Activity Code fields are also verified as being valid. Transactions with invalid fields are rejected and a list of rejected transactions can be printed along with an error code indicating why it was rejected.

101.00,RJB,,L110,A101,02/19/03,1.50,60.00,90.00, "Office conference with Karen Barrett and all 
        of the apartment managers concerning the unpaid rents at the new apartments."
200.01,1,$23,,,02/15/03,0.00,0.00,15.00, "court filing fee."
101.00,MLJ,$,L110,E101,02/15/03,0.00,0.00,1.25, "photocopies."
101.00,MLJ,,L120,A106,02/19/03,1.22,0.00,73.20, "Telephone conference with Ms. Barrett."
200.01,2,$21,,,02/19/03,0.00,0.00,2.50, "Photocopy originals."
200.02,2,$23,,,02/19/03,0.00,0.00,25.00, "Pay County Court filing fee in advance on behalf 
        of Client."