The following is a sample file layout for the XPRTCONV.EXE program.
Program: XPRTCONV.EXE
Data File: DBCHARGE.OUT or INTRANS.SND
File Type: Fixed Length
Note: There is only one difference between the DBCHARGE.OUT and INTRANS.SND
files. The DBCHARGE.OUT file stores the transaction amount in columns 3-12
(10 characters starting at column 3) while the INTRANS.SND file stores zeroes
in columns 3-12. If the INTRANS.SND file is being used, the transaction
amount is calculated by taking the copy count times a default rate per copy.
Lower Case Characters: PC-XPRT uses lower case characters as indicators of
different fields in each record. All characters immediately following the
lower case character up to the next lower case character (or the end of the
record) is the actual data in the field.
DBCHARGE.OUT/INTRANS.SND File Layout
Name Start Length Description
-------------------- ----- ------ ---------------------------------------------
Amount 3 10 Amount (for DBCHARGE.OUT file only) - can
have a leading + or - sign. ($1.23 is
stored as +000000123)
Terminal ID 15 1 Used in descriptions if all description
options are turned off in XPRTCONV
Transaction Date 17 6 Transaction date in YYMMDD format
Page Count 35 6 Used in descriptions and in calculating
the amount for INTRANS.SND input file
User ID ? ? The user ID follows a lower case "A" -
used in descriptions if all description
options are turned off in XPRTCONV
Client Code ? ? The client code follows a lower case "B"
Matter Code ? ? The matter code follows a lower case "C"
PC-XPRT Description ? ? The PC-XPRT description follows a lower
case "D" - may be a part of the converted
description depending on how XPRTCONV is
configured
Possible transaction types:
k - Miscellaneous Disbursements
l - Printed Pages (this is a lower case "L")
m - Faxes
Photocopies Notes: All transactions are assumed to be photocopies unless
there is a lower case "K", "L", or "M" in the record.
Miscellaneous Disbursements Notes: The 2 digit code immediately following the
lower case "K" code is converted as the Tabs3 transaction code. In the
third position following the lower case "K", there will b a "C" or a "D" -
a "C" is converted as a credit (a negative transaction amount) while a "D"
is converted as a debit (a positive amount). The disbursement amount is
stored starting at position 10 following the lower case "K" to the end of
the field.
Sample DBCHARGE.OUT data file (the first 3 lines are not part of the file):
1 2 3 4 5 6 7
12345678901234567890123456789012345678901234567890123456789012345678901234
--------------------------------------------------------------------------
<0+0000018500020921014160000020004000185a0100b100c00k28D000000001850>
<0+0000005000020921014152300010001000010a0101b101c00dDEPOSITIONS>
<0+0000010000010921014153000010002000020a0102b123c45>
<0+0000170000010921014160500090018000170a0103b102c00l52>
<0-0000007500010921014161600020001000000a0200b103c00k28C000000000750>
<0+0000000500020921014093400010003000001a0200b200c01>
<0+0000340000011921014084000010001000170a0200b200c02m51dCONTRACTS TO SIGN>
<0+0000005000010921014132400020004000010a0300b200c03>
<0+0000066000011921014151600000001000033a0400b300c00m50>
<0+0000000000011921014154100000001000000a0402b400c00>
===============================================================================
Validation File: The XPRTCONV program can create a client validation file
named UPDATE.REC in 2 different formats, depending on whether a PC-XPRT
Partner system is in use. There will be a record in the validation file for
each active client in Tabs3.
Format for non-Partner systems:
-------------------------------
CL,F2
AD,F2,<client code>,<matter code>
AD,F2,<client code>,<matter code>
AD,F2,<client code>,<matter code>
.
. (and so on for all clients in Tabs3)
.
BK
Format for Partner systems:
---------------------------
A|A|<client code>|<matter code>|<client name>|<work description>|<bill flag>
A|A|<client code>|<matter code>|<client name>|<work description>|<bill flag>
A|A|<client code>|<matter code>|<client name>|<work description>|<bill flag>
.
. (and so on for all clients in Tabs3)
.
Note: The bill flag will be either "Y" or "N", depending on whether the
client in Tabs3 is configured as billable or non-billable.