syntax check - generic input

[tonym]

Hi Mark,

Would you please verify if the following syntax for .csv generic input is valid?
I have used a blank line input of ",,,,,,,,,,,,," to place a space between certain entries and to separate yearly data for clarity. The reason for using "XX" is to be able to paste the raw data directly from the broker without having to eliminate the columns of data that are not used.

My primary requests are:
1) Is the Split transaction syntax legal?
2) Is the blank line feed legal?
3) If not, does FM require a 0 (zero) between delimiters which are not used?
4) The broker reports commission and SEC fees in separate columns, I then add the two in a new column under the CNUM variable. Is this the best or only way?


MM/DD/YY,XX,MEMO,BNUM,SYMB,ANUM,XX,XX,XX,CNUM,TRAN,ITYPE,ACCT,PORT
,,,,,,,,,,,,,
5/5/2006,2277232094,Bought 6000 JDSU @ 3.4,6000,JDSU,3.4,9.99,-20409.99,,9.99,BUY,Stock,12345,ACCT_12345
6/12/2006,2317501545,Bought 7000 JDSU @ 2.56,7000,JDSU,2.56,9.99,-17929.99,,9.99,BUY,Stock,12345,ACCT_12345
,,,,,,,,,,,,,
10/17/2006,,1:8 Reverse Split,8,JDSU,0.125,,,,,SPLIT,Stock,12345,ACCT_12345
,,,,,,,,,,,,,
2/6/2007,2620135613,Sold 1625 JDSU @ 16.2006,1625,JDSU,16.2006,9.99,26315.18,0.81,10.80,SELL,Stock,12345,ACCT_12345


Thank you for your time.

[Mark]

Hi tonym,

1) Almost... You need to have a number for CNUM. CNUM cannot be blank. Just put a 0 for CNUM, and then the SPLIT line is valid.

2) Yes, you can have blank lines, FM just ignores them.

3) You need to have numbers for ANUM, BNUM, and CNUM, but the XX values can be blank.

4) Yes, this is the best (and only) way to do it. FM only has a single "commission", it doesn't track SEC fees separately from commission fees.