[Kmymoney-devel] [Bug 308247] KMymoney crashes on importing QIF

[Denis]

https://bugs.kde.org/show_bug.cgi?id=308247

--- Comment #14 from Denis <spaarks at gmail.com> ---
You are right the  $-23.97 split should not be there, because a transfer
should not have a split. My mistake in entering it. I corrected all such
incorrect entries but it still crashes. Attached is the corrected file.
I wonder if there are some residual files causing this. I removed KMyMoney
and associated apps, and as many residual files in the KMyMoney folder
(there are some I am unable to delete). Reinstalled and still crashes.
I will try importing qif file with no transfers and no splits.

On Sat, Oct 13, 2012 at 9:25 AM, allan <agander93 at gmail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=308247
>
> --- Comment #12 from allan <agander93 at gmail.com> ---
> (In reply to comment #9)
> > I am not familiar with the structure of .qif files, but I will copy your
> > comments to MoneyManager (which incidentally cannot import split
> > transactions properly, even from its own qif files).
> >
> > I am attaching a larger qif file which contains many more varied
> > transactions than the previous one. It is a US account but with UK style
> > date dd-mm-yyyy.
>
> Another crash, again because of a split problem. --
> D13/08/2012
> T-23.97
> PPaypal USA
> N
> LTransfer
> MOBDII analyser, Fridge thermometers
> $-23.97
> SHome:Miscellaneous
> $9.00
> EHome:Miscellaneous 9.00
> SCar:Maintenance
> $14.97
> ECar:Maintenance 14.97
> ^
> I believe the $-23.97 split is the problem - it shouldn't be there.  The
> following six lines compose two good transactions, but the presence of the
> additional $-23.97 split line causes them to get mis-matched, resulting in
> the
> crash.  Removing that line allows the rest if the file to import without
> problem, the remaining splits being OK.
>
> So far as the crash is concerned, again it shouldn't happen, and I think
> I've
> fixed this too.
>
> I've needed to do some more tuning of extractSplits() to allow the unedited
> file to import, with just that one transaction flagged as unbalanced, and
> in
> need of user attention.
>
> I still have a residual problem, with one of my test files, containing
> three
> splits, where the second split, which has no memo, picks up the memo from
> the
> preceeding split, but that should be simple, I think/hope, then more
> testing.
>
> --
> You are receiving this mail because:
> You reported the bug.
>

-- 
You are receiving this mail because:
You are the assignee for the bug.