Ascom Hasler AMS 24 Interface Program
Version 1.1
Overview
The ASCOM interface program is used to convert expense transactions from an Ascom Hasler AMS 24 Mail Management System to be compatible with the TABS III Merge Data Capture Transactions program. The ASCOM interface program works with the following Ascom Hasler AMS 24 MMS systems:
1) MMS version prior to 4.4E
2) MMS version 4.4E or later
3) WinMMS
This program can also create a client validation file that can be used by the Ascom Hasler AMS 24 system. This file will contain a record for each active client/matter that exists in the TABS III Client file.
Note: The Create Validation Files program must be run before you can successfully use this data capture device interface program. The Create Validation Files program is found in TABS III by selecting the following menu options Maintenance|Integration|Create Validation Files. When creating validation files, select a Validation File Type of Data Capture Device.
Installation
The Ascom interface program (Ascom.EXE) must be transferred to the directory on your hard disk where the TABS III program files reside. This is done by using the INSTALL program on the Ascom Hasler AMS 24
interface program disk.To install the Ascom Hasler AMS 24
interface program on your hard disk:A:
INSTALL
Note: The INSTALL program has a built-in search feature that will find where your TABS III program files reside. On larger network hard drives, this search feature can take quite a bit of time. If you know where the TABS III program files reside, you can bypass this search feature by entering the path following the install command. For example, if the TABS III program files reside on drive F: in a directory named "STI", you would enter: INSTALL F:\STI
Executing the Ascom Hasler AMS 24 Interface Program
Use the following procedure for conversion:
ASCOM
Note: You can specify the input file name when running the ASCOM program. For example, if the input file name is DATA.TXT, you could enter "ASCOM DATA.TXT" (without the quotes). If you don't specify the input file name, the ASCOM program will prompt you for the file name later.
1) MMS version prior to 4.4E
2) MMS version 4.4E or later
3) WinMMS
Note: Both the options entered in Steps 3 and 4 are stored in a parameter file named ASCOM.PRM. Each time the ASCOM program is executed, it will read the ASCOM.PRM file and use those options automatically.
If you enter "CV" (for Create Validation File), and you are using TABS III version 3.4 or later, this routine will create a client validation data file name CLIENT.DAT. This file will contain a record for each active client/matter that exists in the TABS III Client file.
If you enter "CD" (for Convert Data), the program will look for the data file containing the Ascom Hasler AMS 24 data. If the file is found to contain data, the program will display the message "Converting Transactions" followed by a counter as each transaction is read from the file. The files T3EXPKEY.REM, T3EXP.REM, and T3EDESC1.REM will be created which can be merged with the main TABS III data files. You must then start TABS III and run the Merge Data Capture Transactions program.
Note: If you are not using a demo version of the program, the data file will automatically be deleted when the conversion is complete to avoid double posting the data.
Note: If any records in the data file are rejected for any reason, they will be noted in the ASCOM.ERR file. You can look at this file after the ASCOM program executes to see which records (if any) were not converted. If no records are rejected, the ASCOM.ERR file is not created.
Note: You may change default system type or the cost transaction code used by the Ascom Hasler AMS 24 interface program by deleting the ASCOM.PRM file which is created in your TABS III directory. This will enable you to go through the setup procedure described above in Steps 3 and 4 as a first time user of the program.