duplicate checks when importing from .qif

[Steve Neuharth]

	It doesn't seem like there's really any intellegence involved: just check
the check number field in the qif and compare the amount with any
existing check in the register and viola!
	Anyway... do you only import your .qif immediately before you reconcile?
I was planning on reconciling every month (when I recieve my statement)
and downloading a .qif from my bank every week or so to make sure I'm on
top of things.
	If I import the qif now, some of the checks are picked up
by the dupe checker and some are not (not sure why some are and some are
not). I end up having to manually trace old check numbers, delete the
original and then edit the details of the new "cleared" check to reflect
reality. It seems like I must be making this much more difficult than
the authors intended so PLEASE let me know if there is an easier way or
if I'm misunderstanding how gnucash should work.

 > No, it doesn't.  Quicken doesn't, either  Neither one has human
 > intelligence.
 >
 > Actually I find the dupes quite handy.  I can go to the "reconcile"
 > window and if I see one put there by the bank, I know that it is
 > cleared. I then mark the original entry as cleared and delete the
 > dupe.  In my case, the bank entries have the check number in the
 > "Particulars" column, so it is easy to separate them out.
 >
 >> OK... I'm a fairly new user so please bear with me. I'm wanting to
 >> use gnucash as a check register but occasionally download qif's
 >> from my bank to make sure that I haven't missed anything. I did
 >> and import last week and everything seemed fine. I did an import
 >> today and the import duplicated all the checks that had cleared my
 >> bank instead of "divining" that check #4444 that was D/L'd is
 >> actually check #4444 that I had entered in my register. Shouldn't
 >> my checks show up in the importer as potential dupes? The only
 >> thing I can figure is that the checks are imported with the name
 >> "CHECK" with a transaction type of "UNSPECIFIED" and the trans
 >> type is throwing the whole thing off. But, you'd think that
 >> gnucash would notice the check number and "figure it out".
 >>