Almost duplicate transactions

[Derek Atkins]

Benoit Grégoire <bock at step.polymtl.ca> writes:

> generic (read:  even for banks not providing proper payee information for the 
> transfer), the importer will have to allow the imported transactions to match 
> against themselves, which isn't hard to implement in the current code 
> (basically a constant to change and a check so a transaction will never match 
> against itself.  However, it opens up a whole new class of very hairy UI 
> problems:  for instance what happens if you set a transaction as matching a 
> second one, and set that second one as matching a third?  Or set a fourth 
> transaction as matching a fifth, but not import the fift?

This is why the QIF import doesn't allow a user a skip a transaction.
If it's new, it MUST be imported (and MUST be balanced!  -- even against
the "Undefined" account).

-derek
-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available