Importing QIF files

[David Carlson]

On 2/3/2015 12:47 PM, David T. wrote:
> Indeed. Under ideal circumstances, the importer would report better,
> but it doesn't. I'm sorry that I don't have any better suggestions.
>
> Good luck.
>
> David
>
> ------------------------------------------------------------------------
> *From:* Mark Wigmore <mawigmore at gmail.com>
> *To:* David T. <sunfish62 at yahoo.com>
> *Cc:* David Carlson <david.carlson.417 at gmail.com>;
> "gnucash-user at gnucash.org" <gnucash-user at gnucash.org>
> *Sent:* Tuesday, February 3, 2015 10:39 AM
> *Subject:* Re: Importing QIF files
>
> On 3 February 2015 at 18:28, David T. <sunfish62 at yahoo.com
> <mailto:sunfish62 at yahoo.com>> wrote:
> > Did you verify that your investment transaction entries all had
> appropriate, non-null "N" entries, and that the transactions have
> correct formatting for the "T" entries?
> >
> > You might be able to track down the first problem by searching the
> QIF file for lonely N's--i.e., {CRLF}N{CRLF} (where {CRLF} is your
> OS's line break).
> >
> > With regard to the second error, past users have discovered that
> currency symbols will cause transaction format errors. I believe I
> have also heard that amounts using commas and periods differently than
> the importer expects can cause problems.
>
> The file is 580KB long, I'm not inclined to go searching through that
> for something the importer should assist with. I don't even know what
> the correct formatting should be, that's why we have software to do
> these things for us! All I know is BankTree succeeded where GnuCash
> failed. Sorry.
>
>
>
>
> Mark
>
>

Mark,

David T made a very good suggestion, I suggest that you try it.  If you
have MS Word or Open Office Writer the size of the file is immaterial
and the search for special characters is not hard after you have done it
once.  You may need to find the feature that makes the line breaks
visible (it looks like a paragraph mark under the view menu in Open Office).

You yourself said that the alternative is to split the file into chunks
that will almost guarantee getting every transaction twice.

David C