Generic Import Transaction Matcher empty - revisited

[Andrea Carpani]

Il giorno lun, 21-11-2005 alle 18:16 -0500, James Roman ha scritto:

> Since I don't expect my bank to fix this problem soon, I'll have to come
> up with an way of modifying these numbers to make them unique. Ideally,
> I should probably come up with a way that if I exported overlapping date
> ranges, it would identify them as the same transaction. Anyone have any
> suggestions how I might accomplish this? 

I have a similar problem in that my bank uses 0 as FITID in OFX files
for all transactions this results in a single imported transaction.
I'm creating a perl script that changes FITID for each transaction
setting it to a md5 string

$T{FITID} = md5_hex("$T{TRNTYPE}.$T{TRNAMT}.$T{MEMO}");

I yet have to test it as I'm rebuilding gnucash at the moment.

Question: should FITID be numeric?
I'll find out later...

-- 

andrea at carpani.net
http://www.carpani.net
Andrea Carpani
.a.c.

-- 
Andrea Carpani <ml at carpani.net>