On Fri, 03 Mar 2000, you wrote:
> I'm trying to separate this into a multistage process, so you can see
> what's going to happen and have a chance to tweak the importing
> process before it modifies your gnucash accounts.
Your plan as outlined sounds really nice.
The problem comes when you are
> importing QIF files that you got from your bank that represent a
> partial list of transactions, some of which are already in your
> records and some which aren't.
>
> My idea is to somehow red-flag fishy transactions (ones that could be
> duplicates or half-duplicates), and somehow present these for
> inspection. It's going to be somewhat time-consuming and definitely
> heuristic to do a full check for duplicates, so my initial feeling was
> that I'd make that a "Verify" button on the last dialog page, which
> would let you either detect and do something about this case or just
> ignore it and click on the big OK that sucks everything into the
> engine.
Yes, you hit the nail on the head. This would be analagous to the "approve"
window you get when you download transactions from the financial institution
using Quicken. Perhaps you could also memorize that a given imported
transaction matched previously to a given manually entered transaction, and
use that info to better guess the destination account?
David
--
David Fenyes -- [EMAIL PROTECTED]
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
