Bug 331447 - program quit during qif import
Summary: program quit during qif import
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.6.3
Platform: Mint (Ubuntu based) Linux
: NOR grave
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-02-24 02:31 UTC by scsparky
Modified: 2018-10-27 03:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description scsparky 2014-02-24 02:31:16 UTC
I was importing a quicken qif file (1.4MB) and the program appeared to reach about 68% in last (?) stage when program quit -- window disappeared as did the task bar tab. No error messages or any other indicators. Can restart the program but it does not show any sign of the import.

Reproducible: Always
Comment 1 allan 2014-02-24 11:28:19 UTC
On 24/02/14 02:31, scsparky wrote:
> https://bugs.kde.org/show_bug.cgi?id=331447
>
>              Bug ID: 331447
>             Summary: program quit during qif import
>      Classification: Unclassified
>             Product: kmymoney4
>             Version: 4.6.3
>            Platform: Mint (Ubuntu based)
>                  OS: Linux
>              Status: UNCONFIRMED
>            Severity: grave
>            Priority: NOR
>           Component: general
>            Assignee: kmymoney-devel@kde.org
>            Reporter: scsparky1@verizon.net
>
> I was importing a quicken qif file (1.4MB) and the program appeared to reach
> about 68% in last (?) stage when program quit -- window disappeared as did the
> task bar tab. No error messages or any other indicators. Can restart the
> program but it does not show any sign of the import.
>
> Reproducible: Always
>

With QIF being a very loose 'standard', importing can be troublesome. 
It probably may not be possible to get to the cause of your particular 
problem without access to your file, I'm afraid.  I could possibly be a 
time-out problem with such a fairly large file.  If you are willing to 
send a copy off-line to me, I'll do my best to find the cause. 
Otherwise, see below.

One approach which usually helps is to do the importing in stages.  If 
you still have access to Quicken, you could try exporting in sections 
rather than in a big bang.

If you have investments, the prices can take up a lot of room.  If you 
are reasonably adept at editing files, a QIF file is in text format and 
can easily be pruned, just make sure to retain the '^' separator between 
entries.

Have a look at
http://en.wikipedia.org/wiki/Quicken_Interchange_Format#Data_format, 
which explains the format and gives suggestions on dealing with importing.

Don't hesitate to get back in touch if you're stuck.

Allan
Comment 2 Alvaro Soliverez 2014-02-24 11:29:59 UTC
It's also recommended that you upgrade to 4.6.4, which has several fixes for imports.
Comment 3 scsparky 2014-02-25 04:28:43 UTC
(In reply to comment #1)
> On 24/02/14 02:31, scsparky wrote:
> > https://bugs.kde.org/show_bug.cgi?id=331447
> >
> >              Bug ID: 331447
> >             Summary: program quit during qif import
> >      Classification: Unclassified
> >             Product: kmymoney4
> >             Version: 4.6.3
> >            Platform: Mint (Ubuntu based)
> >                  OS: Linux
> >              Status: UNCONFIRMED
> >            Severity: grave
> >            Priority: NOR
> >           Component: general
> >            Assignee: kmymoney-devel@kde.org
> >            Reporter: scsparky1@verizon.net
> >
> > I was importing a quicken qif file (1.4MB) and the program appeared to reach
> > about 68% in last (?) stage when program quit -- window disappeared as did the
> > task bar tab. No error messages or any other indicators. Can restart the
> > program but it does not show any sign of the import.
> >
> > Reproducible: Always
> >
> 
> With QIF being a very loose 'standard', importing can be troublesome. 
> It probably may not be possible to get to the cause of your particular 
> problem without access to your file, I'm afraid.  I could possibly be a 
> time-out problem with such a fairly large file.  If you are willing to 
> send a copy off-line to me, I'll do my best to find the cause. 
> Otherwise, see below.
> 
> One approach which usually helps is to do the importing in stages.  If 
> you still have access to Quicken, you could try exporting in sections 
> rather than in a big bang.
> 
> If you have investments, the prices can take up a lot of room.  If you 
> are reasonably adept at editing files, a QIF file is in text format and 
> can easily be pruned, just make sure to retain the '^' separator between 
> entries.
> 
> Have a look at
> http://en.wikipedia.org/wiki/Quicken_Interchange_Format#Data_format, 
> which explains the format and gives suggestions on dealing with importing.
> 
> Don't hesitate to get back in touch if you're stuck.
> 
> Allan

Thanks for the tip!
I deleted the price records and the file imported, but it is not usable. kmymoney4 complained about not finding many things such as categories. I will try to import in stages with the transaction being the last. However on casual inspection of the quicken qif file not all the categories seem to be exported!

scsparky
Comment 4 Cristian Oneț 2014-07-31 13:23:53 UTC
Did you try importing this with the latest version?
Comment 5 Andrew Crouthamel 2018-09-25 03:50:06 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-27 03:38:35 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!