Bill Gribble writes:
> The kind of duplicate detection you are looking for is in the feature
> list for the next revision of the QIF importer. It's a little
> trickier, because the fields describing the transaction are often very
> different (comparing a hand-entered transaction to a downloaded one)
> and it's hard to determine when two transactions represent the "same
> thing."
I see the difficulty. For my purposes an exact match algorithm would
still be useful, since the original transactions were imported from
the QIF file too. (My bank allows me to download all transactions
from a fixed date only, so updating later in the month includes all of
the earlier transactions).
What do you have in mind for the full facility? A near-miss match
with a query window?
There is one tricky case even for exact matches, which is ATM
withdrawals. It is possible to have two withdrawals for the same
amount on the same date to yield identical transactions. At least my
bank does not record any unique transaction identifier for these.
Keith Refson
--
Dr Keith Refson, "Paradigm is a word too often used by those who would
Dept of Earth Sciences like to have a new idea but cannot think of one."
Parks Road, -- Mervyn King, Deputy Governor, Bank of England
Oxford OX1 3PR, UK
Keith.Refson@ Tel: 01865 272026
earth.ox.ac.uk Fax: 01865 272072
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel