I'm trying to import a QIF file from Quicken 2016 to GnuCash 5.8 on a Windows 11 system. It's a 14 MB QIF file with over 30 years of data. At the first step of the Import process, there are 56 issues reported, all the same: "Could not parse price line". But I just click Next to continue and go on to the next step. I go thru all the remaining steps of the Import process basically just accepting all the default account name mappings. For the selected currency, I'm using USD (US Dollar). At the step for Tradable Commodities, GnuCash appears to have already filled in all the fields (Name, Ticker, Exchange); so at that step I just click Next to continue. And at that point, I click the Start Import button to continue. Then the actual Import process begins. In the first few minutes, the progress bar gets to around 10% of the way across the window. Then things slow down dramatically.
Over the next 2 to 3 hours the progress bar eventually gets to around maybe 20% of the way across the window. I'm not sure how far the progress bar actually gets; since I've never been sitting in front of the screen the whole time to see how far it does get. But when I come back to the computer to check on it, the GnuCash window has closed, with no status or error message on the screen. And when I go and check to see if a .gnucash file was created, there is a file sitting there. But it's extremely small -- just 3 KB in size. And that's clearly a problem; since the original QIF file is 14 MB. I'm a brand new user with GnuCash. This is the first time I'm really trying to use it. And I've tried this Import process now 3 times -- all with the same result. So if anyone out there has some idea what's going on, I'd appreciate any help or suggestions you could provide. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
