I recently went through the process of importing from Quicken and encountered some errors. I exported different date ranges to narrow the problem down and eventually hand edited the lines in the QIF file that had problems. In my case, there were strings of non-alphanumeric characters in the file. I would have to re-export the QIF files to get a better idea where. Since I am running gnucash on Mac OS and the Quicken export files were from Windows, the line numbers in gnucash's error message were off. If I converted the DOS end of line sequence (carriage-return/line-feed) to Mac OS, the line numbers were correct which made it easier to find the line in the QIF file that needed correction.
There was one complex transaction with many splits (I don't remember the Quicken term for this) that I just completely avoided in the Quicken exports and then manually added that transaction in with Gnucash. If this had been more than a one-time task for me, I would have spent more time trying to fix this on the Quicken side -- maybe I had an empty or non-existent name for some account that had been automatically generated using Quicken's direct connect. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
