On Fri, 03 Mar 2000, you wrote:
> Christopher Browne <[EMAIL PROTECTED]> writes:
> > David A Fenyes <[EMAIL PROTECTED]> said:
> > > It would be nice if there is an "import" selection in the register window
> > > itself, which would place the given account at the top of the "guess"
> > > algorithm.
> >
> > Ah, yes. That is indeed a very good observation.
>
> For single-QIF imports, that seems to be the best guess. However, in
> general I think you can do a better job of matching up Quicken
> single-entry transactions with each other by a allowing multiple
> simultaneous QIF file imports and resolving them into splits before
> stuffing them into the engine. In that case, you don't really have
> "The QIF File" to match with "The Selected Account".
>
I suspect that the most common import scenario will be downloaded transactions
from the internet, which will include transactions involving only one account,
with no label, if my bank is any indication (B of A). I'm talking, of course,
about imports after the initial wave of imports (from dumping quicken files
before dumping quicken), which will likely benefit from a fancy algorithm, as
will people trying to episodically synchronize quicken and gnucash.
> In any case, just knowing what account the transactions are with
> respect to doesn't solve all your account-matchup problems; you
> still need to match the destination accounts and categories
> to gnucash accounts.
>
This is true. It would be nice to create categories automatically (I think
this is already done.) That way, Quicken-generated QIF files tend to be
imported quickly, and we don't have to retype in all our expense/income
accounts.
David.
--
David Fenyes -- [EMAIL PROTECTED]
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
